Problem determination in a hybrid environment

• US 9,722,908 B2
• Filed: 10/17/2013
• Issued: 08/01/2017
• Est. Priority Date: 10/17/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Kreuzenstein, Ronald K., Thompson, John G., Knight, Joshua W., Lee, John J., Ruddy, James A., Yudenfriend, Harry M., Chambliss, David D.
• Primary Examiner(s): Dollinger, Tonia L
• Assistant Examiner(s): Belani, Kishin G
• Application Number:
  US14/056,105
• Publication Number:
  US 20150113116A1
• Time in Patent Office: 1,384 Days
• Field of Search: 709224
• CPC Class Codes: G06F 11/0721 within a central processing unit [CPU]
• CPC Class Codes: G06F 11/0778 Dumping, i.e. gathering error/state information after a fault for later diagnosis
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/50 Testing arrangements

Abstract

A multi-mainframe system problem determination method includes recording, in a first computing system, diagnostic data, receiving, in the first computing system, a data collection trigger, responsive to the data collection trigger, coordinating, in the first computing system, synchronized collection of recorded diagnostic data with a second computing system and delivering collected diagnostic data to a storage medium.

Claims

1. A multi-mainframe computing system, comprising:

a first server module running a first operating system;

a second server module communicatively coupled to the first server module, the second server module running a second operating system differing from the first operating system running on the first server module; and

a data storage medium accessible by the first server module and the second server module,

wherein the first server module is configured to solve and identify problems within the multi-mainframe system, and wherein the first server module is configured to;

receive, in the first server module, a data collection trigger;

responsive to the data collection trigger, provide authorized access via an agent to the second server module, and coordinate, in the first server module, synchronized diagnostic data collection with the second server module;

establish a trace data channel to collect the diagnostic data;

establish a session identifier; and

filter the diagnostic data using the session identifier.

2. The system as claimed in claim 1 wherein the first server module is configured to:

record, in the first server module, the diagnostic data; and

deliver the diagnostic data to the data storage medium.

3. The system as claimed in claim 2 wherein the first server module is further configured to:

in response to the trigger, retrieve the trace data associated with the session identifier.

4. The system as claimed in claim 1 wherein the diagnostic data is at least one of trace records, log records and core dumps.