US20040260758A1 - Method for controlling managing computer, medium for storing control program, and managing computer - Google Patents

Method for controlling managing computer, medium for storing control program, and managing computer Download PDF

Info

Publication number
US20040260758A1
US20040260758A1 US10/893,990 US89399004A US2004260758A1 US 20040260758 A1 US20040260758 A1 US 20040260758A1 US 89399004 A US89399004 A US 89399004A US 2004260758 A1 US2004260758 A1 US 2004260758A1
Authority
US
United States
Prior art keywords
computer
information
jobs
managing
managed
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/893,990
Inventor
Toshiaki Hirata
Akihiro Urano
Shuji Fujino
Toshio Sato
Norio Yamamura
Satoshi Miyazaki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US10/893,990 priority Critical patent/US20040260758A1/en
Publication of US20040260758A1 publication Critical patent/US20040260758A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0769Readable error formats, e.g. cross-platform generic formats, human understandable formats
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0748Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a remote unit communicating with a single-box computer node experiencing an error/fault
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3017Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is implementing multitasking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3051Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3065Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3068Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data format conversion
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3065Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3086Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves the use of self describing data formats, i.e. metadata, markup languages, human readable formats
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/069Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324Display of status information
    • G06F11/328Computer systems status display
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466Performance evaluation by tracing or monitoring
    • G06F11/3476Data logging
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/86Event-based monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04Network management architectures or arrangements
    • H04L41/046Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]

Definitions

  • the present application is related to a managing computer connected to a network to which a plurality of computers are connected, for managing these computers. More specifically, the present invention is directed to a technique capable of managing administrate operations executed in the respective computers in a batch mode by the managing computer.
  • Managing computers for managing administrate operations are described in U.S. Pat. No. 5,169,655 entitled to Weng et al., and U.S. Pat. No. 5,642,508 entitled to Miyazawa.
  • the administrate operations involve a job execution process; and a process executed when a specific event occurs.
  • an object of the present invention is to realize such a computer system to which a plurality of computers are connected.
  • a managing computer for managing these computers can manage administrate operations executed in the respective computers are managed in a batch mode.
  • Another object of the present invention is to avoid such that an extra load is given to a network connecting a managing computer group, which is caused by an operation managing computer.
  • a managing computer comprising:
  • an acquiring device for acquiring log information and event information from any of plural computers connected via a network to each other, said log information indicating as to whether or not an execution of an operation process is carried out under normal condition, and said event information indicating concisely as to whether or not an execution of an operation process is carried out under normal condition;
  • a data controller for storing into a database, operation definition information used to define a schedule of process operations executed in said plural computers in relation to said log information and said event information acquired by said acquiring device;
  • acquisition means for acquiring log information indicative of an execution result of an administrate operation executed in each of the computers and also event information indicative of an event occurred in an execution stage of the administrate operation from each of said computers;
  • storage means for into a database, operation definition information in which a schedule of the administrate operations executed in the respective computers, and also the log information and the event information acquired by said acquisition means;
  • display means for displaying the operation definition information related to the respective computers in relation to log information and event information of an administrate operation defined by the operation definition information with reference to the information stored into the database by the storage means.
  • a managing computer connected to a network to which a plurality of computers are connected, for managing these computers, comprising:
  • acquisition means for acquiring log information indicative of an execution result of an administrate operation executed in each of the computers and also event information indicative of an event occurred in an execution stage of the administrate operation from each of said computers;
  • storage means for into a database, operation definition information in which a schedule of the administrate operations executed in the respective computers, and also the log information and the event information acquired by said acquisition means;
  • display means for displaying both a region for describing a list of administrate operations defined by the operation definition information related to each of the computers and also another region for describing log information of said computer on the same screen with reference to the information stored into the database by the storage means. It is possible to display relative information between an event and event definition information together with either of them.
  • a managing computer connected to a network to which a plurality of computers are connected, for managing these computers, comprising:
  • distribution means for distributing the operations definition information
  • acquisition means for acquiring the operation definition information individually formed by the computers from the respective computers and operation definition information in which a portion of the operation definition information distributed by the distribution means and related to the own computer is expanded by the computer from the distributed operation definition information, and also for acquiring log information indicative of an execution result of an administrate operation executed in each of the computers and also event information indicative of an event occurred in an execution stage of the administrate operation from each of said computers;
  • storage means for into a database, the operation definition information acquired by the acquisition means, and also the log information and the event information acquired by the acquisition means;
  • display means for displaying the operation definition information related to the respective computers in relation to log information and event information of an administrate operation defined by the operation definition information with reference to the information stored into the database by the storage means.
  • each of the computers managed by the managing computer many expand the operation definition information of a portion related to the own computer from the operation definition information distributed from the managing computer, and also many convert both the log information and the event information of the administrate operation executed by the own computer into a predetermined common format.
  • the above-explained definition means may define such a computer which should execute the administrate operation by employing predetermined information for indicating all of the computers as to the administrate operations to be executed by all of the computers.
  • the above-described acquisition means may acquire at regular timing, or preselected timing a predetermined sort of log information among the log information of the respective computers, and further may acquire other sorts of log information when these sorts of log information is required to be displayed by the display means.
  • the display means may immediately display either all or a portion of the event information acquired by the acquisition means after being acquired.
  • a “computer” implies not only an apparatus for merely performing a calculation, but also an apparatus for executing a communication process and further various sorts of information process.
  • FIG. 1 schematically shows an overall structural diagram of a computer system according to an embodiment of the present invention
  • FIG. 2 is an explanatory diagram for explaining a system arrangement used to form by a managing computer in operation definition information for defining schedules of administrate operations executed by computers;
  • FIG. 3 is an explanatory diagram for explaining a system arrangement used to manage by the managing computer in both log information of administrate operations and event information, executed by the computers;
  • FIG. 4 schematically represents a hardware structural diagram of the managing computer and the computers
  • FIG. 5 explanatorily indicates a sequential operation for defining/distributing in a batch mode the operation definition information in the system arrangement of FIG. 1, and another sequential operation for acquiring/managing in a batch mode the event information and the log information in the system arrangements of FIG. 3;
  • FIG. 6 is an explanatory diagram for showing an example of the operation definition information defined in a batch mode by the managing computer
  • FIG. 7A and FIG. 7B are explanatory diagrams for indicating an example of the operation definition information of FIG. 6, which has been expanded;
  • FIG. 8 is an explanatory diagram for representing an example of an integrated management screen displayed in the managing computer
  • FIGS. 9A and 9B are explanatory diagrams for showing examples of the event information displayed in the managing computer
  • FIGS. 10A to 10 D are explanatory diagrams for representing examples of structures of various sorts of tables on a database
  • FIG. 11 is a flow chart for describing a process operation after a job is ended under abnormal state
  • FIG. 12 is a diagram for indicating a definition of a process operation after the job is ended under abnormal state.
  • FIG. 13 is a flow chart for explaining a process operation by the managing computer which receives a specific event.
  • FIG. 1 schematically indicates an entire arrangement of a computer system according to an embodiment of the present invention.
  • reference numeral 401 indicates a managing computer
  • reference numerals 402 to 407 represent computers which constitute subjects managed by the managing computer
  • reference numerals 408 to 413 show networks.
  • the managing computer 401 can form in a batch mode operation definition information used to define schedules of administrate operations executed in the computers 402 to 407 , and furthermore the managing computer 401 can manage in a batch mode both log information indicative of execution results obtained from the computers 402 to 407 , and event information indicative of events occurred during execution stage.
  • this managing computer 401 since the managing computer 401 can save the operation definition information, the log information, and the event information in a database form, this managing computer 401 may refer to the above-described information, if necessary, and also may display various items related to the above-explained information.
  • FIG. 2 schematically represents a system arrangement used to form by the managing computer 401 , the operation definition information which defines the schedules of the administrate operations executed by the computers 402 to 407 . It should be understood that although FIG. 2 represents only one computer 402 and the managing computer 401 of FIG. 1, other computers 403 to 407 may be similarly displayed.
  • the managing computer 401 is arranged by a managing application unit 101 , a definition information managing unit 102 , and a database 103 .
  • the managing application unit 101 contains a definition unit 104 and an integrated management screen display unit 105 .
  • the batched definition unit 104 forms operation definition information used to define a schedule of administrate operations executed by the computers 402 to 407 .
  • the integrated management screen display unit 105 displays an integrated management screen (will be discussed later) and so on.
  • the definition information managing unit 102 contains a definition information distributing/acquiring unit 106 for distributing the operation definition information to the computers 402 to 407 , and for acquiring the operation definition information from the computers 402 to 407 .
  • This definition information managing unit 102 stores the operation definition information into the database 103 , and retrieves/referring to the operation definition information stored in the database 103 .
  • each of the computers 402 to 407 is arranged by employing an operation execution unit and an integrated management agent 113 .
  • This operation execution unit contains a job execution control unit 110 , a power supply control unit 111 , a print execution control unit 112 and the like, which execute the administrate operation defined by the operation definition information.
  • the integrated management agent 113 contains a definition information expanding unit 114 and a definition information notifying unit 115 .
  • the definition information expanding unit 114 expands operation definition information of a portion related to the own computer from the operation definition information distributed from the managing computer 401 .
  • the definition information notifying unit 115 notifies to the managing computer 401 , the operation definition information related to the own computer and involving also the operation definition information individually formed by the own computer.
  • FIG. 3 represents a system arrangement in which both log information and event information of administrate operations executed by the computers 402 to 407 are managed in a batch mode by the managing computer 401 .
  • FIG. 3 shows only the managing computer 401 and one computer 402 of FIG. 1, other computers 403 to 407 are similarly applied to this computer 402 .
  • the managing computer 401 is arranged by employing a managing application unit 101 , an event/log managing unit 201 , and a database 103 .
  • the managing application unit 101 contains the integrated management screen display unit 105 for displaying the integrated management screen (will be explained later) and so on.
  • the event/log managing unit 201 contains the event/log acquiring unit 202 for acquiring the event information and the log information from the computers 402 to 407 , and retrieves/refers to the event information and the log information, which are stored in the database 103 . Also, the event/log managing unit 201 stores into the database 103 and outputs to the integrated management screen display unit 105 as to event information which should be notified in real time to an operation manager and so on.
  • each of the computers 402 to 407 is arranged by employing an operation execution unit and an integrated management agent 113 .
  • This operation execution unit contains a job execution control unit 110 , a power supply control unit 111 , a print execution control unit 112 and the like, which execute the administrate operation defined by the operation definition information.
  • the integrated management agent 113 contains a normalizing unit 210 and an event/log notifying unit 211 .
  • the normalizing unit 210 converts both log information and event information of administrate operation executed by the own computer into a predetermined common format.
  • the event/log notifying unit 211 notifies the normalized log information and the normalized event information to the managing computer 401 .
  • FIG. 4 schematically indicates a hardware structure of the managing computer 401 and the computers 402 to 407 .
  • each of the computers is arranged by employing a central processing unit 301 , a main storage apparatus 302 , a network control apparatus 305 , a disk control apparatus 307 , and a display control apparatus 309 .
  • the network control apparatus 305 controls input/output of data between this network control apparatus 305 and a network such as a communication line 303 and a local area network 304 .
  • the disk control apparatus 307 controls a disk apparatus 306 and also input/output thereof.
  • the display control apparatus 309 controls a display apparatus 308 and also input/output thereof.
  • the database 103 is realized on the disk apparatus 306 .
  • Other structural blocks are realized in such a way that a program stored in the disk apparatus 306 is loaded by the central processing unit 301 on the main storage apparatus 302 .
  • this program may be recorded on, for instance, a recording medium such as a CD-ROM, and then may be read into a driver (not shown) to be stored into the disk apparatus 306 .
  • FIG. 5 a description will be made of a sequential operation for defining and distributing the operation definition information in the system arrangement of FIG. 2.
  • the definition information managing unit 102 stores into the database 103 , the operation definition information defined by the batched definition unit 104 contained in the managing application unit 101 (step 601 ).
  • the operation definition information stored in the database 103 is distributed to the computers 402 to 407 at preselected timing by the definition information distributing/acquiring unit 106 contained in the definition information managing unit 102 (step 602 ).
  • the definition information expanding unit 114 owned by the integrated management agent 113 expands operation definition information of a portion related to the own computer from the distributed operation definition information.
  • the definition information expanding unit 114 transfers the expanded operation information to the operation execution unit such as the job execution control unit 110 , the power supply control unit 111 , and the print execution control unit 112 (step 603 ).
  • the operation execution unit executes the administrate operation defined by the respective transferred operation definition information (step 604 ).
  • the definition information distributing/acquiring unit 106 of the definition information managing unit 102 acquires from the computers 402 to 407 , the operation definition information related to the computers 402 to 407 and also containing the operation definition information individually formed in the computers 402 to 407 (step 605 ). Subsequently, the definition information managing unit 102 stores the acquired operation definition information into the database 103 (step 606 ).
  • the integrated screen display unit 105 owned by the managing application unit 101 displays an integrated management screen (will be explained later) in response to a reference request issued from an operation manager and the like, the operation definition information stored into the database 103 in this manner will be retrieved/referred by the definition information managing unit 102 .
  • the operation definition information may be acquired in such a way that the definition information distributing/acquiring unit 106 contained in the definition information managing unit 102 in the managing computer 401 periodically issues a command to the computers 402 to 407 .
  • the acquisition of the operation definition information may be realized by such that the definition information notifying unit 115 owned by the integrated management agent 113 in the computers 402 to 407 initiatively notifies the operation definition information to the managing computer 401 at preselected timing.
  • FIG. 6 shows an example of operation definition information which is defined by the managing computer 401 .
  • reference numeral 701 shows operation definition information.
  • a “definition subject 710 ” corresponds to a portion for defining a computer to be defined.
  • the definition subject 710 may designate a group constituted by a plurality of computers, and a single computer. As represented in FIG. 6, it should be understood that when predetermined information (in this case, “default”) is designated in “definition subject 710 ”, this information implies that all of the computers are the definition subjects.
  • a “power supply control ( 711 )” corresponds to a portion used to define an execution schedule of a power supply turning ON/OFF process of a computer to be defined, and a turning OFF method.
  • a “job execution control ( 712 )” corresponds to a portion used to define a job net on a computer to be defined, and a job on the job net.
  • a “job net A” defines that after an execution of a “job A 1 ” has been completed, a “job A 21 ” and a “job A 22 ” are executed in a parallel manner, and then when the executions of both these jobs A 21 and A 22 are completed, a “job A 3 ” is executed.
  • the operation definition information can be formed in a batch manner, on which the schedule of the administrate operation to be executed by the computer is defined.
  • FIG. 7A and FIG. 7B show an example of the operation definition information 701 of FIG. 6 which is expanded by the computer.
  • FIG. 7A and FIG. 7B there are shown operation definition information 801 to 802 which have been expanded in the computers 402 to 407 of FIG. 2.
  • Each of the above-described operation definition information 801 and 802 is transferred to the power supply control unit 111 and the job execution control unit 110 .
  • the normalizing unit 210 owned by the integrated management agent 113 in each of the computers 402 to 407 converts this event, or log information into a common format to which a discrimination of event/log information is added. Then, the converted common format is notified by the event/log notifying unit 211 to the managing computer 401 (step 610 ).
  • the event/log acquiring unit 202 owned by the event/log managing unit 201 stores the notified event information, or the notified log information into the database 103 (step 611 ).
  • the log information is related to an abnormal state occurred during processing operation and includes information related to an abnormal state occurred during processing operation, whereas the event information is such information which is more important and concise than the former and necessary to inform to the manager computer in real time as to an urgent abnormal event occurred in the operation stage to be cared for by an operator.
  • step 612 information may be discriminated as either log information or event information based upon discrimination contained in this information. As another embodiment, this information may be discriminated as either log information or even information based upon the path through which this information is transferred.
  • both the event information and the log information stored in the database 103 are retrieved/referred by the definition information managing unit 102 .
  • the notifications of the event information and the log information may be preferably realized as to such event information with a high real time characteristic (in particular, event information indicative of failure) as follows.
  • the event/log notifying unit 211 owned by the integrated management agent 113 initiatively notifies the event information to the managing computer 401 .
  • the event/log acquiring unit 202 owned by the event/log managing unit 201 may be realized by regularly issuing a command to the computers 402 to 407 .
  • the notification of the log information may be realized by that in the computers 402 to 407 , the event/log notifying unit 211 owned by the integrated management agent 113 initiatively notifies the log information to the managing computer 401 at preselected timing.
  • FIG. 8 a description will be made of one example of an integrated management screen which is displayed by the integrated management screen display unit 103 owned by the managing application unit 101 in the managing computer 401 .
  • the operation manager and the like may grasp the operations conditions of the computer system by utilizing the above-explained information.
  • the integrated management screen display unit 105 owned by the managing application unit 101 causes the definition information managing unit 102 to retrieve/refer to such information which is required by the operation manager to refer to.
  • this integrated management screen display unit 105 forms as integrated management screen by using the retrieved/referred information, and displays the formed integrated management screen on the display apparatus 308 .
  • the operation manager can grasp the operation condition of the computer system by observing the integrated management screen displayed on the display apparatus 308 .
  • a first screen 501 is an integrated management screen used to confirm computers managed by the managing computer 401 and also to confirm a group of these computers.
  • four sets of computers A to D are indicated.
  • the respective computers A to D are displayed as icons.
  • the operation manager double-clicks “computer A ( 502 )” by using a mouse, so that the first screen 501 can be transferred to a second screen 503 .
  • the second screen 503 is an integrated management screen used to confirm an operation condition of “computer A ( 502 )”.
  • a present job execution condition ( 504 ) a list ( 505 ) of a job net whose execution is defined on the “computer A”
  • a list ( 506 ) of log information corresponding to a past operation history are displayed in a message form on this second screen 503 .
  • the operation manager wants to confirm an operation condition related to “job net A” on the second screen 503 , the operation manager double-clicks a column related to “job net A” listed in the job net list 505 by using the mouse, so that the second screen 503 can be transferred to a third screen 507 .
  • the third screen 507 is an integrated management screen related to “job net A” on “computer A”.
  • This integrated management screen indicates such operation definition information on which a series of administrate operations are defined as to “computer A”, i.e., “turning ON of power supply ( 509 )”, “execution of job net A ( 510 )”, and “printing of execution result ( 511 )”.
  • these administrate operations 509 to 511 are displayed as icons. Since a display mode of each of these icons is changed (for instance, color and shape are changed), various sorts of conditions may be displayed such as “not yet executed”, “under execution”, “execution is ended under normal state” and “execution is ended under abnormal state”. In this case, when the display modes of the respective icons are changed by the integrated management screen display unit 105 , the latest event information of the corresponding administrate operations ( 509 to 511 ) is preferably acquired by the event/log acquiring unit 202 owned by the event/log managing unit 201 .
  • the third screen 507 can be transferred to a sixth screen 514 .
  • a fifth screen 512 corresponds to an integrated management screen used to confirm the operation definition information displayed on the third screen ( 507 ) in a calendar format. For example, since the operation manager selects menu of “calendar displays” (not shown) on the third screen 507 , the third screen 507 can be transferred to the fifth screen 512 . In this example, this fifth screen 512 displays that the job seen on the third screen is executed on a date 513 of a hatched portion.
  • a sixth screen 514 is a detailed integrated management screen related to “job net A” on “computer A”.
  • This sixth screen 514 defines such that as to “job net A”, after an execution of “job A 1 ( 515 )” is completed, both “job A 21 ( 516 )” and “job A 22 ( 517 )” are executed in a parallel manner, and when the executions of both “job A 21 ( 516 )” and “job A 22 ( 517 )” are completed, “job A 3 ( 518 )” is executed.
  • these jobs are displayed as icons. Since a display mode of each of these icons is changed (for instance, color is changed), various sorts of conditions may be displayed such as “not yet executed”, “under execution”, “execution is ended under normal state”, and “execution is ended under abnormal state”.
  • the display modes of the respective icons are changed by the integrated management screen display unit 105 , the latest event information of the corresponding administrate operations ( 509 to 511 ) is preferably acquired by the event/log acquiring unit 202 owned by the event/log managing unit 201 .
  • a fourth screen 508 corresponds to an integrated management screen used to confirm a log with respect to each of job nets. For instance, since the operation manager double-clicks a list ( 506 ) of the log information on the second screen 503 , the second screen 503 can be transferred to the fourth screen 508 .
  • the operation manager designates a column related to “job net A” within the job list 505 by clicking this column by using the mouse, this operation manager selects menu of “log display” (not shown). As a result, the second screen 503 may be transferred to another screen (not shown) on which only log information of “job net A” is displayed.
  • the operation manager selects, for example, the corresponding menu within any of the second screen 504 to the sixth screen 514 , the present screen may be transferred to other screens involving such not-shown screens (event information display screen, statistical display screen, operation definition information updating screen etc.). It will be possible to click a certain message shown in screen 508 to additionally display the window 514 or 507 as indicated with arrows.
  • the operation definition information related to the respective computers is displayed in connection with both the log information and the event information of the administrate operations defined by this operation definition information.
  • the operation manager can grasp the operation conditions of the computer system, and furthermore can readily reflect the grasped operation conditions onto a further plan of the operation schedule.
  • the managing computer 401 preferably and immediately displays this notified event information on the display apparatus 308 .
  • a screen displayed in the managing computer 401 is represented in, for instance, FIG. 9A.
  • FIG. 9A represents an example of a screen on which event information of a computer A is displayed as a message among the notified event information.
  • the message is constructed of an importance degree 901 of the event information, day/time 902 to 903 when the event is notified, a computer 904 of a notification source, and a message main body 905 .
  • the managing computer 401 may display all of the notified event information as a message. Alternatively, as indicated in FIG. 9B, the managing computer 401 may display only pre-designated sorts of event information. As a pre-designated basis, the following items may be conceived, e.g., an importance degree; a range for a date and a time instant; a computer of a notification source; a sort of administrate operation; and a pattern of a character string contained in event information.
  • the operation manager may designate a sort of event information displayed as a message by either the managing computer 401 or the respective computers 402 to 407 .
  • the event/log managing unit 201 judges as to whether or not the notified event information is displayed as the message.
  • the event/log managing unit 201 immediately notifies to the integrated management screen display unit 105 owned by the managing application unit 101 , such event information which is judged to be displayed as a message.
  • the integrated management screen display unit 105 displays this judged event information. Therefore, for instance, as represented in FIG. 9, only such event information indicative of a failure may be displayed as a message.
  • event/log managing unit 201 stores the notified event information into the database 103 irrespective of such a judgment result as to whether or not the notified event information is displayed as the message.
  • FIG. 10A and FIG. 10B represent one example of structures of various sorts of tables on the database 103 .
  • reference numeral 1001 shows an event/log table
  • reference numeral 1002 indicates an operation definition table.
  • the event/log table 1001 is such a table used to store thereinto the events and the log information acquired from the computer by the managing computer 401 in a time sequence.
  • a single record is arranged by “identifier ( 1010 )” “computer name ( 1011 )”, “time ( 1012 )”, “event/log sort ( 1013 )”, “identifier ( 1014 )”, and “detailed information ( 1015 )”.
  • the identifier 1010 is for the event information and the log information.
  • the computer name 1011 is a name of a computer for notifying this information.
  • the time 1012 is time when this information is notified.
  • the sort 1013 is the sort of this information.
  • the identifier 1014 is an identifier of operation definition information on which administrate operation where this information is produced is defined.
  • the information 1010 to 1014 other than the detailed information 1015 is normalized as the common format commonly used to all of the event information and the log information by the normalizing unit 210 owned by the integrated management agent 113 .
  • an operation definition table 1002 is constituted by a common table 1003 arranged by an identifier 1016 of operation definition information, a name ( 1017 ) of a computer to be defined, and a sort ( 1018 ) of operation definition information; and also operation definition detailed tables 1004 to 1005 corresponding to the respective sorts ( 1018 ) of the operation definition information.
  • the operation definition detailed table 1004 related to the power supply control is arranged by, for example, an identifier ( 1019 ) of operation definition information; a power supply initiation date ( 1020 ); a power supply initiation time ( 1021 ); and a power supply turn-OFF date ( 1022 ), and also a power supply turn-OFF time ( 1023 ).
  • the operation definition detailed table 1005 related to the job net is arranged by, for instance, an identifier ( 1024 ) of operation definition information; a name ( 1025 ) of a job net; a job net initiation date ( 1026 ); a job net initiation time ( 1027 ); and a structural job ( 1028 ).
  • both the definition information managing unit 102 and the event/log managing unit 201 retrieve the tables 1001 to 1004 shown in FIG. 10A to FIG. 10D based on a language of, for instance, SQL.
  • the integrated management screen display unit 105 owned by the managing application unit 101 can display such a screen as indicated in FIG. 8.
  • the relationship among the event information, the log information, and the operation definition information may be established by employing the identifier ( 1014 ) of the operation definition information contained in the event/log table 1001 and the identifiers 1016 , 1019 ., 1024 of the operation definition information contained in the operation definition table 1002 .
  • this computer system may be operated as follows. First, for example, when a specific job is accomplished under abnormal state while a job net is being executed, after removing a factor for causing this abnormally ended job (e.g., a specific file required to execute a job is not present), the computer system may instruct that this interrupted job is restarted. This instruction may be realized as follows. That is, as indicated in FIG.
  • a specific job and also a specific job net, by which an abnormal end event is previously defined as a trigger may be executed.
  • This alternative method may be realized as follows. That is, as represented in FIG. 12, while the managing computer defines such a process operation which should be executed when a specific event is received ( 1201 ), when the managing computer receives this specific event as shown in FIG. 13 ( 1301 ), this managing computer instructs a subject computer to execute the designated process operation ( 1302 ). Then, the subject computer may execute this instruction ( 1303 ). At this time, the definition of either the job or the job net which should be executed by the subject computer may be transferred to be registered when the instruction is issued. Otherwise, this definition may be previously transferred to be registered.
  • a network traffic can be reduced.
  • the managing computer 401 since the operation definition information, the event information, and the log information are stored in the database form by the managing computer 401 , the managing computer 401 need not acquire the necessary information from the computer every time the operation manager and the like refer to these information.
  • the computers 402 to 407 are set to be defined in a batch mode by the managing computer 401 .
  • other computers which do not constitute a definition subject are connected to the networks 408 to 413 .
  • a method for recognizing a subject computer to be managed by the managing computer 401 for example, there is a method for automatically detecting the integrated management agent 113 assembled into the computer by using, for example, a broadcasting method.
  • a subject computer to be defined may be previously defined on the managing computer 401 .
  • the operation definition information in which the schedule of the administrate operations executed by the computers 402 to 407 is defined can be formed in a batch mode by the managing computer 401 , and furthermore both the log information and the event information of the administrate operations executed by the computers 402 to 407 can be managed by the managing computer 401 , resulting in better results.
  • the operation manager may grasp the operation condition of the computer system.

Abstract

A managing computer is provided having an acquiring device for acquiring log information and event information from among a plurality of computers via a network to each other into a common database of the managing computer. A data controller may be provided for storing into the common database of the managing computer, operation definition information used to define a schedule of process operations executed in the plurality of computers in relation to the log information and the event information acquired by the acquiring device. A display device may display the operation definition information in relation to event information related to a process operation defined by the operation defining information with reference to the information stored in the database.

Description

  • The present application is a continuation of application Ser. No. 09/793,970, filed Feb. 28, 2001; which is a continuation of application Ser. No. 09/179,091, filed Oct. 27, 1998, now U.S. Pat. No. 6,219,701, the contents of which are incorporated herein by reference.[0001]
  • BACKGROUND OF THE INVENTION
  • The present application is related to a managing computer connected to a network to which a plurality of computers are connected, for managing these computers. More specifically, the present invention is directed to a technique capable of managing administrate operations executed in the respective computers in a batch mode by the managing computer. [0002]
  • Managing computers for managing administrate operations are described in U.S. Pat. No. 5,169,655 entitled to Weng et al., and U.S. Pat. No. 5,642,508 entitled to Miyazawa. The administrate operations involve a job execution process; and a process executed when a specific event occurs. [0003]
  • In a large-scaled computer system wherein a plurality of administrate operations may be combined with each other to be executed, since definitions as to the respective administrate operations must be separately performed and also execution results must be independently confirmed, the management for the total computer system can be hardly carried out. [0004]
  • More specifically, in a large-scaled computer system, there are certain possibilities that a plurality of administrate operations which are executed in combination with each other are executed over a plurality of computers. Under such a circumstance, in order to realize a total management as a computer system, processed contents as to all of administrate operations may be preferably defined and execution results thereof may be preferably confirmed by using a single computer, namely a single managing computer. [0005]
  • However, in the case that the definitions of the processed contents and the confirmations of the execution results as to all of the administrate operations may be performed by one managing computer, since the managing computer must be communicated with the respective computers, a specific care should be paid to the network traffics. [0006]
  • SUMMARY OF THE INVENTION
  • Therefore, an object of the present invention is to realize such a computer system to which a plurality of computers are connected. In this computer system, a managing computer for managing these computers can manage administrate operations executed in the respective computers are managed in a batch mode. [0007]
  • Furthermore, another object of the present invention is to avoid such that an extra load is given to a network connecting a managing computer group, which is caused by an operation managing computer. [0008]
  • To achieve the above-described object, there is provided a managing computer comprising: [0009]
  • an acquiring device for acquiring log information and event information from any of plural computers connected via a network to each other, said log information indicating as to whether or not an execution of an operation process is carried out under normal condition, and said event information indicating concisely as to whether or not an execution of an operation process is carried out under normal condition; [0010]
  • a data controller for storing into a database, operation definition information used to define a schedule of process operations executed in said plural computers in relation to said log information and said event information acquired by said acquiring device; and [0011]
  • a display device for displaying said operation definition information in relation to event information related to a process operation defined by said operation definition information with reference to the information stored in said database. It is possible to provide a managing computer, according to a first aspect of the present invention, is featured by such a managing computer connected to a network to which a plurality of computers are connected, for managing these computers, comprising: [0012]
  • acquisition means for acquiring log information indicative of an execution result of an administrate operation executed in each of the computers and also event information indicative of an event occurred in an execution stage of the administrate operation from each of said computers; [0013]
  • storage means for into a database, operation definition information in which a schedule of the administrate operations executed in the respective computers, and also the log information and the event information acquired by said acquisition means; and [0014]
  • display means for displaying the operation definition information related to the respective computers in relation to log information and event information of an administrate operation defined by the operation definition information with reference to the information stored into the database by the storage means. [0015]
  • Also, a managing computer, according to a second aspect of the present invention, is featured by such a managing computer connected to a network to which a plurality of computers are connected, for managing these computers, comprising: [0016]
  • acquisition means for acquiring log information indicative of an execution result of an administrate operation executed in each of the computers and also event information indicative of an event occurred in an execution stage of the administrate operation from each of said computers; [0017]
  • storage means for into a database, operation definition information in which a schedule of the administrate operations executed in the respective computers, and also the log information and the event information acquired by said acquisition means; and [0018]
  • display means for displaying both a region for describing a list of administrate operations defined by the operation definition information related to each of the computers and also another region for describing log information of said computer on the same screen with reference to the information stored into the database by the storage means. It is possible to display relative information between an event and event definition information together with either of them. [0019]
  • Also, a managing computer, according to a third aspect of the present invention, is featured by such a managing computer connected to a network to which a plurality of computers are connected, for managing these computers, comprising: [0020]
  • definition means for forming in a batch mode both a schedule of each of administrate operations and operation definition information in which a computer which should execute each of the administrate operations is defined; [0021]
  • distribution means for distributing the operations definition information; [0022]
  • acquisition means for acquiring the operation definition information individually formed by the computers from the respective computers and operation definition information in which a portion of the operation definition information distributed by the distribution means and related to the own computer is expanded by the computer from the distributed operation definition information, and also for acquiring log information indicative of an execution result of an administrate operation executed in each of the computers and also event information indicative of an event occurred in an execution stage of the administrate operation from each of said computers; [0023]
  • storage means for into a database, the operation definition information acquired by the acquisition means, and also the log information and the event information acquired by the acquisition means; and [0024]
  • display means for displaying the operation definition information related to the respective computers in relation to log information and event information of an administrate operation defined by the operation definition information with reference to the information stored into the database by the storage means. [0025]
  • It should be understood that each of the computers managed by the managing computer according to the third aspect many expand the operation definition information of a portion related to the own computer from the operation definition information distributed from the managing computer, and also many convert both the log information and the event information of the administrate operation executed by the own computer into a predetermined common format. [0026]
  • Also, in the third aspect, the above-explained definition means may define such a computer which should execute the administrate operation by employing predetermined information for indicating all of the computers as to the administrate operations to be executed by all of the computers. [0027]
  • Also, in any of the first aspect to the third aspect, the above-described acquisition means may acquire at regular timing, or preselected timing a predetermined sort of log information among the log information of the respective computers, and further may acquire other sorts of log information when these sorts of log information is required to be displayed by the display means. [0028]
  • Also, in any of the first aspect to the third aspect, the display means may immediately display either all or a portion of the event information acquired by the acquisition means after being acquired. [0029]
  • It should also be understood in this specification that a “computer” implies not only an apparatus for merely performing a calculation, but also an apparatus for executing a communication process and further various sorts of information process.[0030]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • For a more better understanding of the present invention, reference is made of a detailed description to be read in conjunction with the accompanying drawings; in which: [0031]
  • FIG. 1 schematically shows an overall structural diagram of a computer system according to an embodiment of the present invention; [0032]
  • FIG. 2 is an explanatory diagram for explaining a system arrangement used to form by a managing computer in operation definition information for defining schedules of administrate operations executed by computers; [0033]
  • FIG. 3 is an explanatory diagram for explaining a system arrangement used to manage by the managing computer in both log information of administrate operations and event information, executed by the computers; [0034]
  • FIG. 4 schematically represents a hardware structural diagram of the managing computer and the computers; [0035]
  • FIG. 5 explanatorily indicates a sequential operation for defining/distributing in a batch mode the operation definition information in the system arrangement of FIG. 1, and another sequential operation for acquiring/managing in a batch mode the event information and the log information in the system arrangements of FIG. 3; [0036]
  • FIG. 6 is an explanatory diagram for showing an example of the operation definition information defined in a batch mode by the managing computer; [0037]
  • FIG. 7A and FIG. 7B are explanatory diagrams for indicating an example of the operation definition information of FIG. 6, which has been expanded; [0038]
  • FIG. 8 is an explanatory diagram for representing an example of an integrated management screen displayed in the managing computer; [0039]
  • FIGS. 9A and 9B are explanatory diagrams for showing examples of the event information displayed in the managing computer; [0040]
  • FIGS. 10A to [0041] 10D are explanatory diagrams for representing examples of structures of various sorts of tables on a database;
  • FIG. 11 is a flow chart for describing a process operation after a job is ended under abnormal state; [0042]
  • FIG. 12 is a diagram for indicating a definition of a process operation after the job is ended under abnormal state; and [0043]
  • FIG. 13 is a flow chart for explaining a process operation by the managing computer which receives a specific event.[0044]
  • DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Referring now to drawings, embodiment modes of the present invention will be described. [0045]
  • FIG. 1 schematically indicates an entire arrangement of a computer system according to an embodiment of the present invention. In this drawing, [0046] reference numeral 401 indicates a managing computer; reference numerals 402 to 407 represent computers which constitute subjects managed by the managing computer; and reference numerals 408 to 413 show networks.
  • In the computer system according to this embodiment, the managing [0047] computer 401 can form in a batch mode operation definition information used to define schedules of administrate operations executed in the computers 402 to 407, and furthermore the managing computer 401 can manage in a batch mode both log information indicative of execution results obtained from the computers 402 to 407, and event information indicative of events occurred during execution stage.
  • As a result, since the managing [0048] computer 401 can save the operation definition information, the log information, and the event information in a database form, this managing computer 401 may refer to the above-described information, if necessary, and also may display various items related to the above-explained information.
  • FIG. 2 schematically represents a system arrangement used to form by the managing [0049] computer 401, the operation definition information which defines the schedules of the administrate operations executed by the computers 402 to 407. It should be understood that although FIG. 2 represents only one computer 402 and the managing computer 401 of FIG. 1, other computers 403 to 407 may be similarly displayed.
  • As indicated in FIG. 2, the managing [0050] computer 401 is arranged by a managing application unit 101, a definition information managing unit 102, and a database 103.
  • The managing [0051] application unit 101 contains a definition unit 104 and an integrated management screen display unit 105. The batched definition unit 104 forms operation definition information used to define a schedule of administrate operations executed by the computers 402 to 407. The integrated management screen display unit 105 displays an integrated management screen (will be discussed later) and so on. The definition information managing unit 102 contains a definition information distributing/acquiring unit 106 for distributing the operation definition information to the computers 402 to 407, and for acquiring the operation definition information from the computers 402 to 407. This definition information managing unit 102 stores the operation definition information into the database 103, and retrieves/referring to the operation definition information stored in the database 103.
  • As indicated in FIG. 2, each of the [0052] computers 402 to 407 is arranged by employing an operation execution unit and an integrated management agent 113. This operation execution unit contains a job execution control unit 110, a power supply control unit 111, a print execution control unit 112 and the like, which execute the administrate operation defined by the operation definition information.
  • The integrated [0053] management agent 113 contains a definition information expanding unit 114 and a definition information notifying unit 115. The definition information expanding unit 114 expands operation definition information of a portion related to the own computer from the operation definition information distributed from the managing computer 401. The definition information notifying unit 115 notifies to the managing computer 401, the operation definition information related to the own computer and involving also the operation definition information individually formed by the own computer.
  • FIG. 3 represents a system arrangement in which both log information and event information of administrate operations executed by the [0054] computers 402 to 407 are managed in a batch mode by the managing computer 401. Although FIG. 3 shows only the managing computer 401 and one computer 402 of FIG. 1, other computers 403 to 407 are similarly applied to this computer 402.
  • As indicated in FIG. 3, the managing [0055] computer 401 is arranged by employing a managing application unit 101, an event/log managing unit 201, and a database 103.
  • The managing [0056] application unit 101 contains the integrated management screen display unit 105 for displaying the integrated management screen (will be explained later) and so on. The event/log managing unit 201 contains the event/log acquiring unit 202 for acquiring the event information and the log information from the computers 402 to 407, and retrieves/refers to the event information and the log information, which are stored in the database 103. Also, the event/log managing unit 201 stores into the database 103 and outputs to the integrated management screen display unit 105 as to event information which should be notified in real time to an operation manager and so on.
  • As indicated in FIG. 3, each of the [0057] computers 402 to 407 is arranged by employing an operation execution unit and an integrated management agent 113. This operation execution unit contains a job execution control unit 110, a power supply control unit 111, a print execution control unit 112 and the like, which execute the administrate operation defined by the operation definition information.
  • The integrated [0058] management agent 113 contains a normalizing unit 210 and an event/log notifying unit 211. The normalizing unit 210 converts both log information and event information of administrate operation executed by the own computer into a predetermined common format. The event/log notifying unit 211 notifies the normalized log information and the normalized event information to the managing computer 401.
  • FIG. 4 schematically indicates a hardware structure of the managing [0059] computer 401 and the computers 402 to 407.
  • As indicated in FIG. 4, each of the computers is arranged by employing a [0060] central processing unit 301, a main storage apparatus 302, a network control apparatus 305, a disk control apparatus 307, and a display control apparatus 309. The network control apparatus 305 controls input/output of data between this network control apparatus 305 and a network such as a communication line 303 and a local area network 304. The disk control apparatus 307 controls a disk apparatus 306 and also input/output thereof. The display control apparatus 309 controls a display apparatus 308 and also input/output thereof.
  • Among the structural blocks of FIG. 2 and FIG. 3, the [0061] database 103 is realized on the disk apparatus 306. Other structural blocks are realized in such a way that a program stored in the disk apparatus 306 is loaded by the central processing unit 301 on the main storage apparatus 302. It should be noted that this program may be recorded on, for instance, a recording medium such as a CD-ROM, and then may be read into a driver (not shown) to be stored into the disk apparatus 306.
  • Referring now to FIG. 5, a description will be made of a sequential operation for defining and distributing the operation definition information in the system arrangement of FIG. 2. [0062]
  • As indicated in FIG. 5, in the managing [0063] computer 401, the definition information managing unit 102 stores into the database 103, the operation definition information defined by the batched definition unit 104 contained in the managing application unit 101 (step 601). The operation definition information stored in the database 103 is distributed to the computers 402 to 407 at preselected timing by the definition information distributing/acquiring unit 106 contained in the definition information managing unit 102 (step 602).
  • In the [0064] computers 402 to 407 to which the operation definition information is distributed, the definition information expanding unit 114 owned by the integrated management agent 113 expands operation definition information of a portion related to the own computer from the distributed operation definition information. The definition information expanding unit 114 transfers the expanded operation information to the operation execution unit such as the job execution control unit 110, the power supply control unit 111, and the print execution control unit 112 (step 603). The operation execution unit executes the administrate operation defined by the respective transferred operation definition information (step 604).
  • On the other hand, in the managing [0065] computer 401, the definition information distributing/acquiring unit 106 of the definition information managing unit 102 acquires from the computers 402 to 407, the operation definition information related to the computers 402 to 407 and also containing the operation definition information individually formed in the computers 402 to 407 (step 605). Subsequently, the definition information managing unit 102 stores the acquired operation definition information into the database 103 (step 606).
  • In the case that the integrated [0066] screen display unit 105 owned by the managing application unit 101 displays an integrated management screen (will be explained later) in response to a reference request issued from an operation manager and the like, the operation definition information stored into the database 103 in this manner will be retrieved/referred by the definition information managing unit 102.
  • It should be understood that the operation definition information may be acquired in such a way that the definition information distributing/acquiring [0067] unit 106 contained in the definition information managing unit 102 in the managing computer 401 periodically issues a command to the computers 402 to 407. Alternatively, the acquisition of the operation definition information may be realized by such that the definition information notifying unit 115 owned by the integrated management agent 113 in the computers 402 to 407 initiatively notifies the operation definition information to the managing computer 401 at preselected timing.
  • FIG. 6 shows an example of operation definition information which is defined by the managing [0068] computer 401. In this drawing, reference numeral 701 shows operation definition information.
  • In a definition of the [0069] operation definition information 701, a “definition subject 710” corresponds to a portion for defining a computer to be defined. The definition subject 710 may designate a group constituted by a plurality of computers, and a single computer. As represented in FIG. 6, it should be understood that when predetermined information (in this case, “default”) is designated in “definition subject 710”, this information implies that all of the computers are the definition subjects.
  • A “power supply control ([0070] 711)”corresponds to a portion used to define an execution schedule of a power supply turning ON/OFF process of a computer to be defined, and a turning OFF method. A “job execution control (712)” corresponds to a portion used to define a job net on a computer to be defined, and a job on the job net. In the example of FIG. 6, a “job net A” defines that after an execution of a “job A1” has been completed, a “job A21” and a “job A22” are executed in a parallel manner, and then when the executions of both these jobs A21 and A22 are completed, a “job A3” is executed.
  • As previously explained, since the operation manager and the like designate such a computer for executing the schedule of the respective administrate operations and also the respective administrate operations in the managing [0071] computer 401, the operation definition information can be formed in a batch manner, on which the schedule of the administrate operation to be executed by the computer is defined.
  • FIG. 7A and FIG. 7B show an example of the [0072] operation definition information 701 of FIG. 6 which is expanded by the computer. In FIG. 7A and FIG. 7B, there are shown operation definition information 801 to 802 which have been expanded in the computers 402 to 407 of FIG. 2. Each of the above-described operation definition information 801 and 802 is transferred to the power supply control unit 111 and the job execution control unit 110.
  • Next, a sequential operation for acquiring and for managing in a batch mode the event information and the log information in the system arrangement of FIG. 3 will now be described with reference to FIG. 5. [0073]
  • As indicated in FIG. 5, in such a case that either the event information or the log information notified from the administrate operation unit is equal to a preselected sort of information which should be notified to the managing [0074] computer 401, the normalizing unit 210 owned by the integrated management agent 113 in each of the computers 402 to 407 converts this event, or log information into a common format to which a discrimination of event/log information is added. Then, the converted common format is notified by the event/log notifying unit 211 to the managing computer 401 (step 610).
  • In the managing [0075] computer 401 to which either the event information or the log information is notified, the event/log acquiring unit 202 owned by the event/log managing unit 201 stores the notified event information, or the notified log information into the database 103 (step 611). The log information is related to an abnormal state occurred during processing operation and includes information related to an abnormal state occurred during processing operation, whereas the event information is such information which is more important and concise than the former and necessary to inform to the manager computer in real time as to an urgent abnormal event occurred in the operation stage to be cared for by an operator. As a result, in the case that the event information is notified, it is preferable to immediately display this event information on the display apparatus 308 by the integrated management screen display unit 105 owned by the managing application unit 101 (step 612). It should also be noted that information may be discriminated as either log information or event information based upon discrimination contained in this information. As another embodiment, this information may be discriminated as either log information or even information based upon the path through which this information is transferred.
  • As explained above, in the case that the integrated management [0076] screen display unit 105 owned by the managing application unit 101 displays an integrated management screen (will be explained later) in response to a reference request sent from the operation manager, both the event information and the log information stored in the database 103 are retrieved/referred by the definition information managing unit 102.
  • The notifications of the event information and the log information may be preferably realized as to such event information with a high real time characteristic (in particular, event information indicative of failure) as follows. In the [0077] computers 402 to 407, the event/log notifying unit 211 owned by the integrated management agent 113 initiatively notifies the event information to the managing computer 401. As to the notification of the log information, in the managing computer 401, the event/log acquiring unit 202 owned by the event/log managing unit 201 may be realized by regularly issuing a command to the computers 402 to 407. Alternatively, the notification of the log information may be realized by that in the computers 402 to 407, the event/log notifying unit 211 owned by the integrated management agent 113 initiatively notifies the log information to the managing computer 401 at preselected timing.
  • Subsequently, referring now to FIG. 8, a description will be made of one example of an integrated management screen which is displayed by the integrated management [0078] screen display unit 103 owned by the managing application unit 101 in the managing computer 401.
  • As previously explained, since the operation definition information, the event information, and the log information are stored in the [0079] database 103 in the managing computer 401, the operation manager and the like may grasp the operations conditions of the computer system by utilizing the above-explained information. In other words, within the managing computer 401, the integrated management screen display unit 105 owned by the managing application unit 101 causes the definition information managing unit 102 to retrieve/refer to such information which is required by the operation manager to refer to. Then, this integrated management screen display unit 105 forms as integrated management screen by using the retrieved/referred information, and displays the formed integrated management screen on the display apparatus 308. As a result, the operation manager can grasp the operation condition of the computer system by observing the integrated management screen displayed on the display apparatus 308.
  • In FIG. 8, a [0080] first screen 501 is an integrated management screen used to confirm computers managed by the managing computer 401 and also to confirm a group of these computers. In this example, four sets of computers A to D are indicated. The respective computers A to D are displayed as icons. For example, in the first screen 501, the operation manager double-clicks “computer A (502)” by using a mouse, so that the first screen 501 can be transferred to a second screen 503.
  • Also, in FIG. 8, the [0081] second screen 503 is an integrated management screen used to confirm an operation condition of “computer A (502)”. With respect to the “computer A (502)”, a present job execution condition (504), a list (505) of a job net whose execution is defined on the “computer A”, and a list (506) of log information corresponding to a past operation history are displayed in a message form on this second screen 503. For example, when the operation manager wants to confirm an operation condition related to “job net A” on the second screen 503, the operation manager double-clicks a column related to “job net A” listed in the job net list 505 by using the mouse, so that the second screen 503 can be transferred to a third screen 507.
  • Also, in FIG. 8, the [0082] third screen 507 is an integrated management screen related to “job net A” on “computer A”. This integrated management screen indicates such operation definition information on which a series of administrate operations are defined as to “computer A”, i.e., “turning ON of power supply (509)”, “execution of job net A (510)”, and “printing of execution result (511)”.
  • It should be noted that these [0083] administrate operations 509 to 511 are displayed as icons. Since a display mode of each of these icons is changed (for instance, color and shape are changed), various sorts of conditions may be displayed such as “not yet executed”, “under execution”, “execution is ended under normal state” and “execution is ended under abnormal state”. In this case, when the display modes of the respective icons are changed by the integrated management screen display unit 105, the latest event information of the corresponding administrate operations (509 to 511) is preferably acquired by the event/log acquiring unit 202 owned by the event/log managing unit 201.
  • For example, when “job net A ([0084] 501)” is double-clicked by using the mouse by the operation manager, the third screen 507 can be transferred to a sixth screen 514.
  • Also, in FIG. 8, a [0085] fifth screen 512 corresponds to an integrated management screen used to confirm the operation definition information displayed on the third screen (507) in a calendar format. For example, since the operation manager selects menu of “calendar displays” (not shown) on the third screen 507, the third screen 507 can be transferred to the fifth screen 512. In this example, this fifth screen 512 displays that the job seen on the third screen is executed on a date 513 of a hatched portion.
  • Also, in FIG. 8, a [0086] sixth screen 514 is a detailed integrated management screen related to “job net A” on “computer A”. This sixth screen 514 defines such that as to “job net A”, after an execution of “job A1 (515)” is completed, both “job A21 (516)” and “job A22 (517)” are executed in a parallel manner, and when the executions of both “job A21 (516)” and “job A22 (517)” are completed, “job A3 (518)” is executed.
  • It should also be noted that these jobs are displayed as icons. Since a display mode of each of these icons is changed (for instance, color is changed), various sorts of conditions may be displayed such as “not yet executed”, “under execution”, “execution is ended under normal state”, and “execution is ended under abnormal state”. In this case, when the display modes of the respective icons are changed by the integrated management [0087] screen display unit 105, the latest event information of the corresponding administrate operations (509 to 511) is preferably acquired by the event/log acquiring unit 202 owned by the event/log managing unit 201.
  • Also, in FIG. 8, a [0088] fourth screen 508 corresponds to an integrated management screen used to confirm a log with respect to each of job nets. For instance, since the operation manager double-clicks a list (506) of the log information on the second screen 503, the second screen 503 can be transferred to the fourth screen 508.
  • Alternatively, for example, while the operation manager designates a column related to “job net A” within the [0089] job list 505 by clicking this column by using the mouse, this operation manager selects menu of “log display” (not shown). As a result, the second screen 503 may be transferred to another screen (not shown) on which only log information of “job net A” is displayed.
  • It should be understood that when the operation manager selects, for example, the corresponding menu within any of the [0090] second screen 504 to the sixth screen 514, the present screen may be transferred to other screens involving such not-shown screens (event information display screen, statistical display screen, operation definition information updating screen etc.). It will be possible to click a certain message shown in screen 508 to additionally display the window 514 or 507 as indicated with arrows.
  • As previously explained, in accordance with this embodiment, in the managing [0091] computer 401, the operation definition information related to the respective computers is displayed in connection with both the log information and the event information of the administrate operations defined by this operation definition information. As a consequence the operation manager can grasp the operation conditions of the computer system, and furthermore can readily reflect the grasped operation conditions onto a further plan of the operation schedule.
  • As previously described, after the event information is notified, the managing [0092] computer 401 preferably and immediately displays this notified event information on the display apparatus 308. At this time, a screen displayed in the managing computer 401 is represented in, for instance, FIG. 9A.
  • FIG. 9A represents an example of a screen on which event information of a computer A is displayed as a message among the notified event information. In this drawing, the message is constructed of an [0093] importance degree 901 of the event information, day/time 902 to 903 when the event is notified, a computer 904 of a notification source, and a message main body 905.
  • The managing [0094] computer 401 may display all of the notified event information as a message. Alternatively, as indicated in FIG. 9B, the managing computer 401 may display only pre-designated sorts of event information. As a pre-designated basis, the following items may be conceived, e.g., an importance degree; a range for a date and a time instant; a computer of a notification source; a sort of administrate operation; and a pattern of a character string contained in event information. The operation manager may designate a sort of event information displayed as a message by either the managing computer 401 or the respective computers 402 to 407.
  • Then, in the managing [0095] computer 401, the event/log managing unit 201 judges as to whether or not the notified event information is displayed as the message. The event/log managing unit 201 immediately notifies to the integrated management screen display unit 105 owned by the managing application unit 101, such event information which is judged to be displayed as a message. Then, the integrated management screen display unit 105 displays this judged event information. Therefore, for instance, as represented in FIG. 9, only such event information indicative of a failure may be displayed as a message. It should be understood that event/log managing unit 201 stores the notified event information into the database 103 irrespective of such a judgment result as to whether or not the notified event information is displayed as the message.
  • FIG. 10A and FIG. 10B represent one example of structures of various sorts of tables on the [0096] database 103. In the drawings, reference numeral 1001 shows an event/log table, and reference numeral 1002 indicates an operation definition table.
  • The event/log table [0097] 1001 is such a table used to store thereinto the events and the log information acquired from the computer by the managing computer 401 in a time sequence. A single record is arranged by “identifier (1010)” “computer name (1011)”, “time (1012)”, “event/log sort (1013)”, “identifier (1014)”, and “detailed information (1015)”. The identifier 1010 is for the event information and the log information. The computer name 1011 is a name of a computer for notifying this information. The time 1012 is time when this information is notified. The sort 1013 is the sort of this information. The identifier 1014 is an identifier of operation definition information on which administrate operation where this information is produced is defined. In the computer, the information 1010 to 1014 other than the detailed information 1015 is normalized as the common format commonly used to all of the event information and the log information by the normalizing unit 210 owned by the integrated management agent 113.
  • As indicated in FIG. 10B to FIG. 10D, an operation definition table [0098] 1002 is constituted by a common table 1003 arranged by an identifier 1016 of operation definition information, a name (1017) of a computer to be defined, and a sort (1018) of operation definition information; and also operation definition detailed tables 1004 to 1005 corresponding to the respective sorts (1018) of the operation definition information.
  • The operation definition detailed table [0099] 1004 related to the power supply control is arranged by, for example, an identifier (1019) of operation definition information; a power supply initiation date (1020); a power supply initiation time (1021); and a power supply turn-OFF date (1022), and also a power supply turn-OFF time (1023). The operation definition detailed table 1005 related to the job net is arranged by, for instance, an identifier (1024) of operation definition information; a name (1025) of a job net; a job net initiation date (1026); a job net initiation time (1027); and a structural job (1028).
  • In the managing [0100] computer 401, both the definition information managing unit 102 and the event/log managing unit 201 retrieve the tables 1001 to 1004 shown in FIG. 10A to FIG. 10D based on a language of, for instance, SQL. As a result, the integrated management screen display unit 105 owned by the managing application unit 101 can display such a screen as indicated in FIG. 8. In particular, the relationship among the event information, the log information, and the operation definition information may be established by employing the identifier (1014) of the operation definition information contained in the event/log table 1001 and the identifiers 1016, 1019., 1024 of the operation definition information contained in the operation definition table 1002.
  • It should be noted that when the screen is displayed, in such a case that information required to be displayed is not present in the tables [0101] 1001 to 1004 of FIG. 10, the managing computer 401 is operated in a similar manner to that shown in FIG. 5 so as to acquire this information required to be displayed.
  • In the case that such information indicative of a failure occurred in operation conditions of the computer system is notified as an event, this computer system may be operated as follows. First, for example, when a specific job is accomplished under abnormal state while a job net is being executed, after removing a factor for causing this abnormally ended job (e.g., a specific file required to execute a job is not present), the computer system may instruct that this interrupted job is restarted. This instruction may be realized as follows. That is, as indicated in FIG. 11, in the managing computer, “reexecution command” for designating “subject computer”, “job net name”, “job name to be reexecuted” is entered ([0102] 1101); this command is transferred to the above-explained subject computer (1102) so as to be executed (1103). Secondly, the computer system may instruct this job net to be canceled. This second idea may be realized as follows. That is, as shown in FIG. 11, in the managing computer, “cancel command” for designating “subject computer” and “job net name” is entered (1101); this command is transferred to the above-described subject computer (1102) so as to be executed (1103). Furthermore, thirdly, when a specific job is ended under abnormal state while a job net is being executed, a specific job and also a specific job net, by which an abnormal end event is previously defined as a trigger, may be executed. This alternative method may be realized as follows. That is, as represented in FIG. 12, while the managing computer defines such a process operation which should be executed when a specific event is received (1201), when the managing computer receives this specific event as shown in FIG. 13 (1301), this managing computer instructs a subject computer to execute the designated process operation (1302). Then, the subject computer may execute this instruction (1303). At this time, the definition of either the job or the job net which should be executed by the subject computer may be transferred to be registered when the instruction is issued. Otherwise, this definition may be previously transferred to be registered.
  • Subsequently, a description will now be made of effects achieved in such a case that the operation definition information, the event information, and the log information are processed in the database form by the managing [0103] computer 401 to be stored.
  • As a first effect, a network traffic can be reduced. In accordance with the present invention, since the operation definition information, the event information, and the log information are stored in the database form by the managing [0104] computer 401, the managing computer 401 need not acquire the necessary information from the computer every time the operation manager and the like refer to these information.
  • For instance, in the network structure of FIG. 1, when log information of 1 K bytes is acquired from each of the six [0105] computers 402 to 407 by the managing computer at a frequency of 1,000 messages/day, a network traffic of 6 M bytes/day is produced. In the case that the log information is referred by the operation manager at a frequency of 10 times/day, a network traffic of 60 M bytes/day in total is produced.
  • Furthermore, as to such log information with a low demand of a real-time characteristic, if such log information is collected within such a time range where the normal network traffic is low, for example, in a night time range, the network traffic reduction effect can be apparently achieved. [0106]
  • As a second effect, since the operation definition information, the event information, and the log information are stored in the database form by the managing [0107] computer 401, as represented in the integrated management screen of FIG. 8, there is another effect that the above-explained information can be readily displayed in various relationship aspects.
  • In the computer system according to this embodiment, the [0108] computers 402 to 407 are set to be defined in a batch mode by the managing computer 401. However, it is conceivable that other computers which do not constitute a definition subject are connected to the networks 408 to 413. In this case, as a method for recognizing a subject computer to be managed by the managing computer 401, for example, there is a method for automatically detecting the integrated management agent 113 assembled into the computer by using, for example, a broadcasting method. As another method, a subject computer to be defined may be previously defined on the managing computer 401.
  • Also, in accordance with the computer system according to this embodiment, the operation definition information in which the schedule of the administrate operations executed by the [0109] computers 402 to 407 is defined can be formed in a batch mode by the managing computer 401, and furthermore both the log information and the event information of the administrate operations executed by the computers 402 to 407 can be managed by the managing computer 401, resulting in better results. Alternatively, if at least both the log information and the event information can be managed, then the operation manager may grasp the operation condition of the computer system.

Claims (37)

1 (canceled).
2. A managing computer to be connected to a plurality of managed computers via a network, said managing computer comprising:
a network interface to be connected to the network; and
a processing unit to be connected to the network interface,
wherein said processing unit sends to the managed computers, via the network interface, definition information including information that has been set defining details of a plurality of jobs included in a group of jobs to be executed by the managed computers and an identifier of the definition information, receives, via the network interface, result information resulting from execution of each job by one of the managed computers, said result information including an identifier of the job executed by the managed computer, and displays on a display said result information resulting from execution of each of said jobs included in said group of jobs according to said definition information.
3. A managing computer according to claim 2, wherein each job for a respective managed computer is performed after a power ON condition and before a power OFF condition of the respective managed computer.
4. A managing computer according to claim 2, wherein said processing unit selects result information resulting from execution of a pre-designated job.
5. A managing computer according to claim 2, wherein said processing unit selects result information resulting from execution of said jobs having a pre-defined pattern.
6. A managing computer according to claim 2, wherein said definition information includes information defining a schedule for executing said jobs.
7. A managing computer according to claim 2, wherein said definition information includes information designating which managed computer is to execute which one of said jobs.
8. A managing computer to be connected to a plurality of managed computers via a network, said managing computer comprising:
a network interface to be connected to the network; and
a processing unit to be connected to the network interface,
wherein said processing unit sends to the managed computers, via the network interface, definition information including information that has been set defining details of a plurality of jobs included in a group of jobs to be executed by one of the managed computers and an identifier of the definition information, receives, via the network interface, result information resulting from execution of each job by one of the managed computers, said result information including an identifier of the job executed by the managed computer, and displays on a display said result information resulting from execution of each of said jobs included in said group of jobs according to said definition information.
9. A managing computer according to claim 8, wherein each job for a respective managed computer is performed after a power ON condition and before a power OFF condition of the respective managed computer.
10. A managing computer according to claim 8, wherein said processing unit selects result information resulting from execution of a pre-designated job.
11. A managing computer according to claim 8, wherein said processing unit selects result information resulting execution of said jobs having a pre-defined pattern.
12. A managing computer according to claim 8 wherein said definition information includes information defining a schedule for executing said jobs.
13. A managing computer according to claim 8, wherein said definition information includes information designating which managed computer is to execute said jobs.
14. A method of managing a plurality of managed computers via a network, said method comprising the steps of:
sending to the managed computers definition information including information that has been set defining details of a plurality of jobs included in a group of jobs to be executed by the managed computers and an identifier of the definition information;
receiving result information resulting from execution of each job by one of the managed computers, said result information including an identifier of the job executed by the managed computer; and
displaying on a display said result information resulting from execution of each of said jobs included in said group of jobs according to said definition information.
15. A method according to claim 14, wherein each job for a respective managed computer is performed after a power ON condition and before a power OFF condition of the respective managed computer.
16. A method according to claim 14, further comprising the step of:
selecting result information resulting from execution of a pre-designated job.
17. A method according to claim 14, further the steps of:
selecting result information resulting from execution of said jobs having a pre-defined pattern.
18. A method according to claim 14, wherein said definition information includes information defining a schedule for executing said jobs.
19. A method according to claim 14, wherein said definition information includes information designating which managed computer is to execute which one of said jobs.
20. A method of managing a plurality of managed computers via a network, said managing computer comprising the steps of:
sending to the managed computers definition information including information that has been set defining details of a plurality of jobs included in a group of jobs to be executed by one of the managed computers and an identifier of the definition information;
receiving result information resulting from execution of each job by one of the managed computers, said result information including an identifier of the job executed by the managed computer; and
displaying on a display said result information resulting from execution of each of said jobs included in said group of jobs according to said definition information.
21. A method according to claim 20, wherein each job for a respective managed computer is performed after a power ON condition and before a power OFF condition of the respective managed computer.
22. A method according to claim 20, further comprising the step of:
selecting result information resulting from execution of a pre-designated job.
23. A method according to claim 20, further comprising the steps of:
selecting result information resulting from execution of said jobs having a pre-defined pattern.
24. A method according to claim 20, wherein said definition information includes information defining a schedule for executing said jobs.
25. A method according to claim 20, wherein said definition information includes information designating which managed computer is to execute said jobs.
26. A computer system comprising:
a network;
a managing computer; and
a plurality of managed computers,
wherein said managing and managed computers are connected to each other by said network, and
wherein said managing computer comprises:
a network interface to be connected to the network, and
a processing unit to be connected to the network interface,
wherein said processing unit sends to the managed computers, via the network interface, definition information including information that has been set defining details of a plurality of jobs included in a group of jobs to be executed by the managed computers and an identifier of the definition information, receives, via the network interface, result information resulting from execution of each job by one of the managed computers, said result information including an identifier of the job executed by the managed computer, and displays on a display said result information resulting from execution of each of said jobs included in said group of jobs according to said definition information.
27. A computer system according to claim 26, wherein each job for a respective managed computer is performed after a power ON condition and before a power OFF condition of the respective managed computer.
28. A computer system according to claim 26, wherein said processing unit selects result information resulting from execution of a pre-designated job.
29. A computer system according to claim 26, wherein said processing unit selects result information resulting from execution of said jobs having a pre-defined pattern.
30. A computer system according to claim 26, wherein said definition information includes information defining a schedule for executing said jobs.
31. A computer system according to claim 26, wherein said definition information includes information designating which managed computer is to execute which one of said jobs.
32. A computer system comprising:
a network;
a managing computer; and
a plurality of managed computers,
wherein said managing and managed computers are connected to each other by said network, and
wherein said managing computer comprises:
a network interface to be connected to the network, and
a processing unit to be connected to the network interface,
wherein said processing unit sends to the managed computers, via the network interface, definition information including information that has been set defining details of a plurality of jobs included in a group of jobs to be executed by one of the managed computers and an identifier of the definition information, receives, via the network interface, result information resulting from execution of each job by one of the managed computers, said result information including an identifier of the job executed by the managed computer, and displays on a display said result information resulting from execution of each of said jobs included in said group of jobs according to said definition information.
33. A computer system according to claim 32, wherein each job for a respective managed computer is performed after a power ON condition and before a power OFF condition of the respective managed computer.
34. A computer system according to claim 32, wherein said processing unit selects result information resulting from execution of a pre-designated job.
35. A computer system according to claim 32, wherein said processing unit selects result information resulting execution of said jobs having a pre-defined pattern.
36. A computer system according to claim 32, wherein said definition information includes information defining a schedule for executing said jobs.
37. A computer system according to claim 32, wherein said definition information includes information designating which managed computer is to execute said jobs.
US10/893,990 1997-10-27 2004-07-20 Method for controlling managing computer, medium for storing control program, and managing computer Abandoned US20040260758A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/893,990 US20040260758A1 (en) 1997-10-27 2004-07-20 Method for controlling managing computer, medium for storing control program, and managing computer

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
JP29403097A JP3614625B2 (en) 1997-10-27 1997-10-27 Management manager computer, recording medium, and computer operation management method
JP09-294030 1997-10-27
US09/179,091 US6219701B1 (en) 1997-10-27 1998-10-27 Method for controlling managing computer, medium for storing control program, and managing computer
US09/793,970 US6938082B2 (en) 1997-10-27 2001-02-28 Method for controlling managing computer, medium for storing control program, and managing computer
US10/893,990 US20040260758A1 (en) 1997-10-27 2004-07-20 Method for controlling managing computer, medium for storing control program, and managing computer

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/793,970 Continuation US6938082B2 (en) 1997-10-27 2001-02-28 Method for controlling managing computer, medium for storing control program, and managing computer

Publications (1)

Publication Number Publication Date
US20040260758A1 true US20040260758A1 (en) 2004-12-23

Family

ID=17802364

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/179,091 Expired - Lifetime US6219701B1 (en) 1997-10-27 1998-10-27 Method for controlling managing computer, medium for storing control program, and managing computer
US09/793,970 Expired - Fee Related US6938082B2 (en) 1997-10-27 2001-02-28 Method for controlling managing computer, medium for storing control program, and managing computer
US10/893,990 Abandoned US20040260758A1 (en) 1997-10-27 2004-07-20 Method for controlling managing computer, medium for storing control program, and managing computer

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US09/179,091 Expired - Lifetime US6219701B1 (en) 1997-10-27 1998-10-27 Method for controlling managing computer, medium for storing control program, and managing computer
US09/793,970 Expired - Fee Related US6938082B2 (en) 1997-10-27 2001-02-28 Method for controlling managing computer, medium for storing control program, and managing computer

Country Status (3)

Country Link
US (3) US6219701B1 (en)
EP (1) EP0913774A3 (en)
JP (1) JP3614625B2 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050235288A1 (en) * 2004-04-20 2005-10-20 Takashi Yamakabe Method and system for controlling computer resources
US20070130119A1 (en) * 2005-12-01 2007-06-07 Phillips Brent R User/process runtime system trace
US20070130320A1 (en) * 2005-12-01 2007-06-07 Morgan Fabian F Efficient, centralized management of application log configuration settings
US20080209402A1 (en) * 2007-02-27 2008-08-28 Red Hat, Inc. Non-invasive time-based profiling tool
EP1837771A3 (en) * 2006-03-17 2009-07-15 Iontas Limited Monitoring of computer events
US20090249345A1 (en) * 2008-03-31 2009-10-01 Qualcomm Incorporated Operating System Fast Run Command
EP2902908A4 (en) * 2012-09-28 2016-07-06 Hitachi Ltd System operation trace method in distributed system

Families Citing this family (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3614625B2 (en) * 1997-10-27 2005-01-26 株式会社日立製作所 Management manager computer, recording medium, and computer operation management method
JP3537356B2 (en) * 1998-12-09 2004-06-14 株式会社日立製作所 Delay factor analysis method in job system
US6711612B1 (en) * 1998-12-18 2004-03-23 Emc Corporation System for facilitating the transfer of management information from a remote mass storage subsystem over a switching fabric or selectively over a private link to a central location for servicing
JP2000259585A (en) * 1999-03-08 2000-09-22 Toshiba Corp System application management system and recording medium stored with program for executing the system
US6718378B1 (en) * 1999-04-30 2004-04-06 Canon Kabushiki Kaisha Device management information processing apparatus method and storage medium
KR100510068B1 (en) * 1999-06-22 2005-08-26 주식회사 하이닉스반도체 System for monitoring automization system to produce semiconductor and method using the same
US6381642B1 (en) 1999-10-21 2002-04-30 Mcdata Corporation In-band method and apparatus for reporting operational statistics relative to the ports of a fibre channel switch
KR20010057732A (en) * 1999-12-23 2001-07-05 오길록 Method for processing signal on distributed environment
US6594786B1 (en) * 2000-01-31 2003-07-15 Hewlett-Packard Development Company, Lp Fault tolerant high availability meter
GB2362231B (en) * 2000-05-08 2002-08-14 3Com Corp Storage of data relating to events in a network
JP2002049855A (en) * 2000-05-24 2002-02-15 Sony Computer Entertainment Inc Server system
JP3614091B2 (en) * 2000-08-11 2005-01-26 日本電気株式会社 Job schedule operation management apparatus, job schedule operation management method, and program recording medium
JP3626458B2 (en) 2001-06-04 2005-03-09 株式会社ソニー・コンピュータエンタテインメント Log collection analysis system, log collection method, log collection program to be executed by computer, log analysis method, log analysis program to be executed by computer, log collection device, log analysis device, log collection terminal, log server
CN100386755C (en) * 2001-06-22 2008-05-07 英维思系统股份有限公司 Method and system for collecting and retrieving time-series, real-time and non-real-time data
US7774435B2 (en) * 2001-07-26 2010-08-10 Oracle America, Inc. System and method for batch tuning intelligent devices
US7305674B2 (en) * 2001-08-31 2007-12-04 International Business Machines Corporation Method and apparatus to manage multi-computer supply
JP2003099295A (en) * 2001-09-21 2003-04-04 Teamgia:Kk Processing method for communication log, computer software program for implementing the same method on computer system and communication log processing system
CA2365729A1 (en) * 2001-12-20 2003-06-20 Platform Computing (Barbados) Inc. Topology aware scheduling for a multiprocessor system
US7154857B1 (en) 2001-12-21 2006-12-26 Mcafee, Inc. Enterprise network analyzer zone controller system and method
US6892227B1 (en) * 2001-12-21 2005-05-10 Networks Associates Technology, Inc. Enterprise network analyzer host controller/zone controller interface system and method
US6789117B1 (en) * 2001-12-21 2004-09-07 Networks Associates Technology, Inc. Enterprise network analyzer host controller/agent interface system and method
CN100361476C (en) * 2002-02-05 2008-01-09 国际商业机器公司 Method for writing, browsing, answering and transmitting E-mail and E-mail customer machine
FR2835629B1 (en) * 2002-02-07 2005-01-28 Bull Sa METHOD AND SYSTEM FOR MANAGING A PERSONAL EVENT LOG EVALUATED TO AN OPERATING ACTIVITY EXECUTED ON A MATERIAL PERIMETER OF COMPUTER RESOURCES AND MEMORY IMPLEMENTED IN SAID SYSTEM
JP4310070B2 (en) 2002-04-26 2009-08-05 株式会社日立製作所 Storage system operation management method
US6760304B2 (en) 2002-10-28 2004-07-06 Silverback Systems, Inc. Apparatus and method for receive transport protocol termination
TWI245514B (en) * 2002-12-20 2005-12-11 Hon Hai Prec Ind Co Ltd System and method for displaying relevant events of networking devices
CA2419305C (en) * 2003-02-20 2006-03-21 Ibm Canada Limited - Ibm Canada Limitee Unified logging service for distributed applications
DE10323369A1 (en) * 2003-05-21 2004-12-16 Vodafone Holding Gmbh Monitoring and coordination device in a computer network
DE102004001323B3 (en) * 2004-01-08 2005-07-07 Conxpert Holding Gmbh Method and device for monitoring the data exchange between application systems
US8209708B2 (en) * 2004-03-25 2012-06-26 International Business Machines Corporation Methods, systems and computer program products for generating events having a common event format
US7546488B2 (en) 2004-07-02 2009-06-09 Seagate Technology Llc Event logging and analysis in a software system
JP4561254B2 (en) * 2004-09-03 2010-10-13 セイコーエプソン株式会社 Device management system
US20060075092A1 (en) * 2004-10-06 2006-04-06 Kabushiki Kaisha Toshiba System and method for determining the status of users and devices from access log information
US7546489B2 (en) 2005-01-25 2009-06-09 Seagate Technology Llc Real time event logging and analysis in a software system
DE602005026773D1 (en) * 2005-03-09 2011-04-21 Sap Ag Logging of cross-system activities in a distributed system
US8239498B2 (en) * 2005-10-28 2012-08-07 Bank Of America Corporation System and method for facilitating the implementation of changes to the configuration of resources in an enterprise
US8782201B2 (en) * 2005-10-28 2014-07-15 Bank Of America Corporation System and method for managing the configuration of resources in an enterprise
JP4758214B2 (en) * 2005-12-08 2011-08-24 株式会社日立製作所 Operation estimation system, operation estimation device, execution device, and operation estimation method
JP4487291B2 (en) * 2006-02-13 2010-06-23 鳴利 田渕 Monitoring result recording system, common log generation device, and program
US10838714B2 (en) 2006-04-24 2020-11-17 Servicenow, Inc. Applying packages to configure software stacks
US7971187B2 (en) * 2006-04-24 2011-06-28 Microsoft Corporation Configurable software stack
US8347291B2 (en) * 2006-12-29 2013-01-01 Sap Ag Enterprise scheduler for jobs performable on the remote system by receiving user specified values for retrieved job definitions comprising metadata representation of properties of jobs
US20080195750A1 (en) * 2007-02-09 2008-08-14 Microsoft Corporation Secure cross platform auditing
US20080229210A1 (en) * 2007-03-14 2008-09-18 Akiko Bamba Display processing system
JP2010524130A (en) * 2007-04-12 2010-07-15 トムソン ライセンシング Centralized workflow monitoring
JP2009230322A (en) * 2008-03-21 2009-10-08 Hitachi Software Eng Co Ltd Job management system
JP2010072846A (en) * 2008-09-17 2010-04-02 Hitachi Software Eng Co Ltd Job operation management system and method
JP5352504B2 (en) * 2010-03-12 2013-11-27 株式会社富士通エフサス Monitoring information processing apparatus and monitoring information processing program
US9299197B2 (en) 2013-03-15 2016-03-29 Bosch Automotive Service Solutions Inc. Graphical user interface with on board and off-board resources
JP2015011361A (en) * 2013-06-26 2015-01-19 富士通株式会社 Job monitoring program, job monitoring method, job monitoring apparatus, and monitoring target apparatus
US10275182B2 (en) 2016-02-24 2019-04-30 Bank Of America Corporation System for categorical data encoding
US10216798B2 (en) 2016-02-24 2019-02-26 Bank Of America Corporation Technical language processor
US10019486B2 (en) 2016-02-24 2018-07-10 Bank Of America Corporation Computerized system for analyzing operational event data
US10430743B2 (en) 2016-02-24 2019-10-01 Bank Of America Corporation Computerized system for simulating the likelihood of technology change incidents
US10067984B2 (en) 2016-02-24 2018-09-04 Bank Of America Corporation Computerized system for evaluating technology stability
US10366337B2 (en) 2016-02-24 2019-07-30 Bank Of America Corporation Computerized system for evaluating the likelihood of technology change incidents
US10223425B2 (en) 2016-02-24 2019-03-05 Bank Of America Corporation Operational data processor
US10366338B2 (en) 2016-02-24 2019-07-30 Bank Of America Corporation Computerized system for evaluating the impact of technology change incidents
US10387230B2 (en) 2016-02-24 2019-08-20 Bank Of America Corporation Technical language processor administration
US10366367B2 (en) 2016-02-24 2019-07-30 Bank Of America Corporation Computerized system for evaluating and modifying technology change events
US10275183B2 (en) 2016-02-24 2019-04-30 Bank Of America Corporation System for categorical data dynamic decoding
JP6760985B2 (en) * 2018-03-06 2020-09-23 ファナック株式会社 Operation management device

Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4323966A (en) * 1980-02-05 1982-04-06 The Bendix Corporation Operations controller for a fault-tolerant multiple computer system
US4873623A (en) * 1985-04-30 1989-10-10 Prometrix Corporation Process control interface with simultaneously displayed three level dynamic menu
US5491791A (en) * 1995-01-13 1996-02-13 International Business Machines Corporation System and method for remote workstation monitoring within a distributed computing environment
US5559955A (en) * 1990-09-17 1996-09-24 Cabletron Systems, Inc. Method and apparatus for monitoring the status of non-pollable device in a computer network
US5619655A (en) * 1993-02-26 1997-04-08 Siemens Aktiengesellschaft System for administration and management of network from remote or central station through an operator interface which prepares and stores the management orders for execution
US5642508A (en) * 1993-05-31 1997-06-24 Nec Corporation Distributed control method and apparatus for job execution
US5655081A (en) * 1995-03-08 1997-08-05 Bmc Software, Inc. System for monitoring and managing computer resources and applications across a distributed computing environment using an intelligent autonomous agent architecture
US5729472A (en) * 1996-05-17 1998-03-17 International Business Machines Corporation Monitoring architecture
US5748884A (en) * 1996-06-13 1998-05-05 Mci Corporation Autonotification system for notifying recipients of detected events in a network environment
US5867716A (en) * 1994-06-14 1999-02-02 Hitachi, Ltd. Distributed computer system and method of generating automatic operation schedule for the same
US5872970A (en) * 1996-06-28 1999-02-16 Mciworldcom, Inc. Integrated cross-platform batch management system
US5893905A (en) * 1996-12-24 1999-04-13 Mci Communications Corporation Automated SLA performance analysis monitor with impact alerts on downstream jobs
US6023507A (en) * 1997-03-17 2000-02-08 Sun Microsystems, Inc. Automatic remote computer monitoring system
US6044394A (en) * 1997-07-21 2000-03-28 International Business Machines Corporation Managing independently executing computer tasks that are interrelated by dataflow
US6085244A (en) * 1997-03-17 2000-07-04 Sun Microsystems, Inc. Dynamic test update in a remote computer monitoring system
US6219701B1 (en) * 1997-10-27 2001-04-17 Hitachi, Ltd. Method for controlling managing computer, medium for storing control program, and managing computer
US6327623B2 (en) * 1997-05-30 2001-12-04 Texas Instruments Incorporated Computer system with environmental detection

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2520129B2 (en) 1987-05-27 1996-07-31 キヤノン株式会社 Information output device
JPH04127352A (en) 1990-09-19 1992-04-28 Fujitsu Ltd Distributed processing system
EP0754321B1 (en) * 1994-04-05 2000-09-06 Intel Corporation Method and appartus for monitoring and controlling programs in a network
JPH08147362A (en) 1994-11-17 1996-06-07 Mitsubishi Electric Corp System controller
JPH08272711A (en) 1995-03-30 1996-10-18 Mitsubishi Electric Corp Automatic management system for file transfer
JP3367305B2 (en) * 1995-11-14 2003-01-14 三菱電機株式会社 Network system

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4323966A (en) * 1980-02-05 1982-04-06 The Bendix Corporation Operations controller for a fault-tolerant multiple computer system
US4873623A (en) * 1985-04-30 1989-10-10 Prometrix Corporation Process control interface with simultaneously displayed three level dynamic menu
US5559955A (en) * 1990-09-17 1996-09-24 Cabletron Systems, Inc. Method and apparatus for monitoring the status of non-pollable device in a computer network
US5619655A (en) * 1993-02-26 1997-04-08 Siemens Aktiengesellschaft System for administration and management of network from remote or central station through an operator interface which prepares and stores the management orders for execution
US5642508A (en) * 1993-05-31 1997-06-24 Nec Corporation Distributed control method and apparatus for job execution
US5867716A (en) * 1994-06-14 1999-02-02 Hitachi, Ltd. Distributed computer system and method of generating automatic operation schedule for the same
US5491791A (en) * 1995-01-13 1996-02-13 International Business Machines Corporation System and method for remote workstation monitoring within a distributed computing environment
US5655081A (en) * 1995-03-08 1997-08-05 Bmc Software, Inc. System for monitoring and managing computer resources and applications across a distributed computing environment using an intelligent autonomous agent architecture
US5729472A (en) * 1996-05-17 1998-03-17 International Business Machines Corporation Monitoring architecture
US5748884A (en) * 1996-06-13 1998-05-05 Mci Corporation Autonotification system for notifying recipients of detected events in a network environment
US5872970A (en) * 1996-06-28 1999-02-16 Mciworldcom, Inc. Integrated cross-platform batch management system
US5893905A (en) * 1996-12-24 1999-04-13 Mci Communications Corporation Automated SLA performance analysis monitor with impact alerts on downstream jobs
US6023507A (en) * 1997-03-17 2000-02-08 Sun Microsystems, Inc. Automatic remote computer monitoring system
US6085244A (en) * 1997-03-17 2000-07-04 Sun Microsystems, Inc. Dynamic test update in a remote computer monitoring system
US6327623B2 (en) * 1997-05-30 2001-12-04 Texas Instruments Incorporated Computer system with environmental detection
US6044394A (en) * 1997-07-21 2000-03-28 International Business Machines Corporation Managing independently executing computer tasks that are interrelated by dataflow
US6219701B1 (en) * 1997-10-27 2001-04-17 Hitachi, Ltd. Method for controlling managing computer, medium for storing control program, and managing computer

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050235288A1 (en) * 2004-04-20 2005-10-20 Takashi Yamakabe Method and system for controlling computer resources
US8046764B2 (en) * 2004-04-20 2011-10-25 Hitachi, Ltd. Redistribution of unused resources assigned to a first virtual computer having usage below a predetermined threshold to a second virtual computer
US8326966B2 (en) 2005-12-01 2012-12-04 International Business Machines Corporation Efficient, centralized management of application log configuration settings
US20070130119A1 (en) * 2005-12-01 2007-06-07 Phillips Brent R User/process runtime system trace
US20070130320A1 (en) * 2005-12-01 2007-06-07 Morgan Fabian F Efficient, centralized management of application log configuration settings
WO2007062887A1 (en) * 2005-12-01 2007-06-07 International Business Machines Corporation User/process runtime system trace
US7996822B2 (en) 2005-12-01 2011-08-09 International Business Machines Corporation User/process runtime system trace
EP1837771A3 (en) * 2006-03-17 2009-07-15 Iontas Limited Monitoring of computer events
US20080209402A1 (en) * 2007-02-27 2008-08-28 Red Hat, Inc. Non-invasive time-based profiling tool
US10127129B2 (en) * 2007-02-27 2018-11-13 Red Hat, Inc. Non-invasive time-based profiling tool
US20090249345A1 (en) * 2008-03-31 2009-10-01 Qualcomm Incorporated Operating System Fast Run Command
KR101250892B1 (en) 2008-03-31 2013-04-04 퀄컴 인코포레이티드 Operating system fast run command
US8151266B2 (en) * 2008-03-31 2012-04-03 Qualcomm Incorporated Operating system fast run command
EP2902908A4 (en) * 2012-09-28 2016-07-06 Hitachi Ltd System operation trace method in distributed system

Also Published As

Publication number Publication date
JP3614625B2 (en) 2005-01-26
EP0913774A2 (en) 1999-05-06
JPH11134306A (en) 1999-05-21
US6938082B2 (en) 2005-08-30
EP0913774A3 (en) 2004-05-12
US20010054094A1 (en) 2001-12-20
US6219701B1 (en) 2001-04-17

Similar Documents

Publication Publication Date Title
US6938082B2 (en) Method for controlling managing computer, medium for storing control program, and managing computer
US6170010B1 (en) Computer operation management system
US6578006B1 (en) Project work management method and system
EP1410566B1 (en) Improved event database management method and system for network event reporting system
US20030065902A1 (en) System and method for storage management
US5787244A (en) Information retrieval system
JPH11143829A (en) Operation managing method of computer system
JP2000040021A (en) Monitoring display system and record medium
US7752169B2 (en) Method, system and program product for centrally managing computer backups
US7155498B1 (en) Computer operation management system
KR100496980B1 (en) A Web Based Integration System Management Tool And The Method Using The Same
JPH10177596A (en) Product development project management system and method
JP3992029B2 (en) Object management method
JP3984948B2 (en) Computer system operation management method
JPH06223020A (en) Network control system and control method for object
JP2004062905A (en) Control manager computer, storage medium, and computer operation control method
JP2000122879A (en) Performance monitoring method for computer system
JP3815494B2 (en) Computer system and operation management method thereof
JP2003228414A (en) Facility monitoring system
JP2988389B2 (en) Monitoring screen restriction method for network monitoring systems
JPH08241277A (en) Unitary management system of resources
JPH05204783A (en) Operation monitoring system
JPH0290257A (en) Terminal attribute switching system for operation of on-line system
Jones Managing Diverse Environments with CA‐UNICENTER for UNIX
JP2002157134A (en) Method and system for cooperatively using and managing job

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION