Skip to main content

Software  >  Rational  >  

Compiled Language Debug extension for Rational Team Concert Client for System z

 News
 
Abstract
The compiled language debug extension for Rational®Team Concert Client for System z (Team Debug) which is installed as part of IBM® Rational® Developer for System z™or later, allows the transfer of compiled language debug sessions between Rational Team Concert team members.
 
Content
1. OVERVIEW
2. PREPARING TO DEBUG
3. TRANSFERRING A TEAM DEBUG SESSION
4. PARKING A TEAM DEBUG SESSION
5. ACCEPTING A TEAM DEBUG SESSION
6. SEARCHING FOR TEAM DEBUG SESSIONS
7. TEAM DEBUG VIEW


1. OVERVIEW

The compiled language debug extension for Rational Team Concert Client for System z (Team Debug) allows the transfer of compiled language debug sessions between Rational Team Concert team members. During a debug session, a team member can decide to transfer the debug session to another team member. The transfer results in the receiver establishing control of the debug session. The session is at the point where the transfer occurred. The receiver can then continue to debug the application from that point.
Transferring your debug session is useful in team environments where different team members are experts or owners of different components of an application. Sharing debug sessions enables faster problem resolution by allowing the transfer of existing debug sessions without the receiver having to establish the correct environment and start the debug session over again.

To use this feature, you must install and configure the following software:
  • Every user must have Rational Developer for System z, Version 7.6 or later, with the debug extension for Rational Team Concert installed.
  • You must install the team debug service extension for IBM Rational Team Concert for System z server.
  • Every user must be connected to the same Rational Team Concert for System z server.


2. PREPARING TO DEBUG

Before beginning a team debug session, you must have a user ID on the Rational Team Concert for System z server and be connected to that server. Anyone you want to transfer a debug session to must also have a user ID on the same Rational Team Concert for System z server and be connected. In addition, you must start your debug daemon and it must be ready to accept incoming debug sessions. Refer to the "Listening for debug connections" topic for instructions on how to work with the debug daemon.

After you have verified that you and the other user are connected to the same Rational Team Concert for System z server, you must read the instructions in http://www-01.ibm.com/support/docview.wss?=&uid=swg21405180. This technote describes one way you can indicate that you want a team debug session to start with Debug Tool for z/OS.

2.1 Starting a team debug session

To start a team debug session with Debug Tool for z/OS, you must follow the directions in technote . Then, you can start the compiled application in the same way you start a normal debug session.

Team debug session looks the same as a normal debug session, with the following differences:
  • The debug target is labeled Platform: [Team] zOS 390X Connection: <host>
  • There are two new context menu actions when you right-click on the debug target:
    • Transfer to User: Transfers the session to another user. Select the user from the list.
    • Park Debug Session: The debug session will be parked on the team repository. Parked sessions are debugged by the user Nobody. These sessions can be debugged by any user by selecting the session in the Team Debug view and choosing the debug action.

2.2 Verifying your connection to Rational Team Concert
To use the team debug function, you must be a member of a Rational® Team Concert team and connected to a Rational Team Concert repository.

To verify you are connected, open the team artifacts view. To do this, select Window->Show View->Other->Team->Team Artifacts. Connections are displayed by expanding Repository Connections.

Refer to the Rational Team Concert documentation for more information on establishing repository connections.


3. TRANSFERRING A TEAM DEBUG SESSION

When you transfer a debug session, Rational Team Concert transfers the debug session and its current state to another user. It transfers the current thread states, breakpoints, and monitors. However, it does not transfer memory monitors nor variable filter settings.

You can transfer a debug session to another user by one of the following methods:
  • Drag and drop the session from the Debug view into a configured instant messaging client supported by Rational Team Concert.
  • In the Debug view, right click on the debug target and select Transfer to User.


3.1 Transfer by using the Transfer to User action

To transfer a debug session to another team member, right-click the debug target that you want to transfer (in the Debug view) and select the Transfer to User action from the context menu. The Transfer to User dialog box will open. In this dialog box, specify the team member to which you want to transfer the session.

If the debug session transfer is successful, you will see the session disconnected from your debugger user interface.

3.2 Transfer using drag and drop

To transfer a debug session using drag and drop, follow these instructions:

1. Open a chat window with the user that you would like to transfer the debug session to.
2. Select the debug target of the team debug session from the Debug view.
3. Hold down the left mouse button while dragging the debug target to the chat window.
4. Release the left mouse button to drop the session into the chat window.
5. You will see that a hyperlink is created in the chat window. Send this hyperlink to the user.

The recipient user will see a hyperlink for the debug session. When the recipient user clicks the hyperlink, you will receive a notification that someone has requested to debug the team debug session. You can decide if the transfer should be allowed at this time. If you allow for the debug session transfer to continue (by responding Yes), the current debug session will be disconnected. The recipient user will receive the debug session.
You will also receive a notification even if you are not currently debugging a debug session. This is to ensure that your debug session is not taken by someone else while you have temporarily stopped debugging an application.
The instant messaging client must be configured to work with Rational Team Concert. Refer to the Rational Team Concert documentation for more information.


4. PARKING A TEAM DEBUG SESSION

Parking a debug session allows you to suspend debugging an application temporarily. The debug session remains in its current state until someone retrieves it from the team repository to continue debugging it.

This feature enables you to:
  • Park the session and resume again later if you are going to be temporarily disconnected.
  • Park a session if the user for the transfer is not currently logged in.
  • Park a session if you do not know who should continue debugging.

A parked debug session does not belong to anybody. Any team member can retrieve a debug a parked debug session from the team repository.

To park a team debug session, right-click the debug target in the Debug view and select Park Debug Session from the context menu. This will disconnect the current debug session.

You can search for parked debug sessions from the Team Artifacts view and from the Team Debug view. For parked debug sessions, the Debugged By column in the Team Debug view will indicate Nobody as the user name. To learn more about searching for team debug sessions, see the related topic.

You can also retrieve and debug a parked debug session from a team repository. You will need to search for the parked debug session and then request to debug the debug session from the Team Debug view. To learn how to start debugging a team debug session, refer to "7. TEAM DEBUG VIEW" topic.


5. ACCEPTING A TEAM DEBUG SESSION

You can receive a team debug session in one of the following two ways:
  • You will receive a notification that someone has transferred a debug session to you. In the notification message, select Yes to accept the transfer.
  • You can receive a hyperlink for a team debug session in a chat window. In this case, click on the hyperlink from the chat window.

When a debug session is transferred to you, the Debug view opens.

A team debug session looks the same as a normal debug session with only a few subtle differences:
  • The process is labeled Platform: [Team] remote_machine_platform Connection: remote_machine_IP_address.
  • There are three new team debug actions available from the debug target context menu:
    • Transfer to User: Transfers the session to another user. Select the user from the list.
    • Park Debug Session: The debug session will be parked on the team repository. Parked sessions are debugged by the user Nobody. These sessions can be debugged by any user by selecting the session in the Team Debug view and choosing the debug action.


6. SEARCHING FOR TEAM DEBUG SESSIONS

The search debug sessions features allow you to find debug sessions that are currently managed by the team repository. You can search for team debug sessions from the Team Artifacts view or the Team Debug view.

To search for debug sessions from the Team Artifacts view:
1. Open the Team Artifacts view.
2. Ensure that you are logged in to the team repository from which you are searching for the team debug sessions.
3. Expand the Debug node.
4. Expand the Search team debug sessions node.
5. Select one of the queries that you would like to run.
6. To run the query, double-click it or select the Search context menu action.

Example
The following predefined queries are available:
  • Started By Me: Lists all sessions started by you.
  • My Current Debug Sessions: Lists all sessions that you can debug.
  • Parked Debug Sessions: Lists all sessions that are currently parked in the team repository.
  • Team Repository: Lists all sessions currently registered in the team repository. When the search is completed, the Team Debug view will open to show the search results.


7. TEAM DEBUG VIEW
The Team Debug view contains a table view of the current team debug sessions. Each row in the table represents one session.

These are the columns in the table:
  • Debug Session: This is the name of the debug session. The name matches the debug launch configuration that started the session.
  • Host: This is the name of the host that the session is currently connected to.
  • Debug Target: This is the name of the host that your program resides on and the port it is connected to (for example, Platform: [Team] remote_machine_platform Connection: remote_machine_IP_address).
  • Team Repository: This is the URL of the Rational Team Concert server that the team debug session is registered to (for example, https://rtcserver.company.com:9443/jazz).
  • Started By: This is the Rational Team Concert user that started the initial debug session.
  • Debugged By: This is the Rational Team Concert user that is currently connected to a debug session. Sessions can be debugged by Nobody, indicating that the session has been parked on the server and is not currently being actively debugged.
  • Started At: This is the time at which the debug session was started.

7.1 Team Debug View Actions
  • Search Team Debug Sessions: Position the mouse pointer over the downward arrow and press the left mouse button to view the predefined queries available for you when searching for team debug sessions from the team repository:
    • Started By Me: Lists all sessions started by you.
    • My Current Debug Sessions: Lists all sessions that you can debug.
    • Parked Debug Sessions: Lists all sessions that are currently parked in the team repository.
    • Team Repository: Lists all sessions currently registered in the team repository.
  • Refresh: Position the mouse pointer over this icon and press the left mouse button to refresh the view’s contents.

7.2 Debug session actions in the Team Debug View:
Each row in the Team Debug View table represents a debug session. Select a row and right mouse click to open the context menu. The following actions are available in this menu:
  • Debug: Allows you start debugging the team debug session. You can only debug a team debug session if your user id is specified in the Debugged By column or if the debug session is currently parked.
  • Remove from Team Repository: This removes the debug session from the team repository. You can only remove a debug session from the team repository if you are the person who started the debug session or you are currently debugging the debug session. For example, you can remove a debug session if your user id is listed in the Debugged By column.
Note: Removing a debug session from the team repository will terminate all connections to that
debug target. This means that Rational Team Concert server disconnects from that target and
clients (users) connected to that debug target are disconnected.
 
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Software Development
 Analysis, Modeling, Design & Construction
 Rational Developer for System z
 Integrations: IBM
 Operating system(s):
  Windows, z/OS
 Software version:
  7.6
 Software edition:
  All Editions
 Reference #:
  1409932
 IBM Group:
 Software Group
 Modified date:
 2009-11-06

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.