Xpediter IMS MPP Launch Configurations

To create an Xpediter IMS MPP launch configuration from Xpediter/Eclipse

  1. From the Run menu, select Debug Configurations. The Debug Configurations dialog box appears. This dialog box contains a tree view of configuration types (such as Xpediter Batch Debug Session) and their corresponding configurations.

    Important

    Alternatively, a launch configuration can be created from Host Explorer or Project Explorer.

  2. In the left pane, select Xpediter IMS MPP Debug Session.

  3. Click icon_add_launch_configuration.gif or right-click the node and select New. A child node representing the newly created configuration is added to the Xpediter IMS MPP Debug Session root node.

    Important

    Alternatively, you can share launch configurations by exporting from one workspace and importing into another workspace.

  4. Enter in the Name field a name for the new configuration. The default name is New_configuration.
  5. Complete the tabs beneath the Name field, which are used to define the launch configuration:
    • Target
    • Visualization (Optional) (Used to request visualization of program and I/O calls in the Runtime Visualizer perspective. For more information refer to the Topaz WorkbenchProgram Analysis and Runtime Visualizer User Guide.)
    • Code Coverage (Optional)
    • Scripting (Optional)
    • Load Libraries (Optional)
    • DDIO (Optional)
    • Log (Optional)
    • Work Files (Optional)
    • Common tab

Important

An error displays at the top of the Debug Configurations dialog box any time a required field of a launch configuration is not specified or is invalid. A debug session using a configuration with errors cannot be launched.

To create an Xpediter IMS MPP launch configuration from Host Explorer or Project Explorer

  1. Do any of the following:

    • Right-click a JCL member in Project Explorer and select Debug As>Xpediter IMS MPP Debug Session.
    • Right-click a JCL member in the Host Explorer navigation tree and select Debug As>Xpediter IMS MPP Debug Session.
    • Right-click a JCL member in the Host Explorer Contents view and select Debug As>Xpediter IMS MPP Debug Session.
    • With the JCL member open in an editor, right-click and select Debug As>Xpediter IMS MPP Debug Session.
    • Select a JCL member and, from the Run menu, select Debug As>Xpediter IMS MPP Debug Session.
    • Select a JCL member and, from the debug_exc.gif list, select Debug As>Xpediter IMS MPP Debug Session.

    The Select Debug Configuration dialog box appears, showing all previous launch configurations of this type.

    Important

    If there are no previous launch configurations that use this JCL, the Debug Configurations dialog box appears, pre-populated with information for a selected JCL member. The default launch configuration name is <JCL member name>. Skip to step 3.

    Important

    If the parse is unsuccessful, the data is not populated.

    Important

    The toolbar and right-click functionality available for a configuration is described in the right pane when a configuration type is selected.

  2. Select Create a new configuration and click Open. The Debug Configurations dialog box appears, pre-populated with information for a selected JCL member. The default launch configuration name is <JCL member name>.
  3. Complete any additional information on the tabs beneath the Name field, which are used to define the launch configuration:
    • Target
    • Visualization (Optional) (Used to request visualization of program and I/O calls in the Runtime Visualizer perspective. For more information refer to the Topaz WorkbenchProgram Analysis and Runtime Visualizer User Guide.)
    • Code Coverage (Optional)
    • Scripting (Optional)
    • Load Libraries (Optional)
    • DDIO (Optional)
    • Log (Optional)
    • Work Files (Optional)
    • Common tab

Important

An error displays at the top of the Debug Configurations dialog box any time a required field of a launch configuration is not specified or is invalid. A debug session using a configuration with errors cannot be launched.

To open an existing launch configuration

  1. In Host Explorer, do any of the following:

    • Right-click a JCL member in Project Explorer and select Debug As>Xpediter IMS MPP Debug Session.
    • Right-click a JCL member in the Host Explorer navigation tree and select Debug As>Xpediter IMS MPP Debug Session.
    • Right-click a JCL member in the Host Explorer Contents view and select Debug As>Xpediter IMS MPP Debug Session.
    • With the JCL member open in an editor, right-click and select Debug As>Xpediter IMS MPP Debug Session.
    • Select a JCL member and, from the Run menu, select Debug As>Xpediter IMS MPP Debug Session.
    • Select a JCL member and, from the debug_exc.gif list, select Debug As>Xpediter IMS MPP Debug Session.

    The Select Debug Configuration dialog box appears, showing all existing launch configurations of this type that use the selected JCL member.

    Important

    If there are no previous launch configurations that use this JCL, the Debug Configurations dialog box appears, pre-populated with information for a selected JCL member, so a new launch configuration can be created. Continue the process of creating a new launch configuration by completing the tabs used to define the launch configuration as described above. The default launch configuration name is <JCL member name>.

  2. Select Use an existing configuration, select the launch configuration from the list, and click Open. The Debug Configurations dialog box appears.

Alternatively, prior launched debug sessions that use a particular configuration can be re-launched using the list menu of the Debug toolbar button on the Xpediter or Host Explorer perspective and selecting the configuration.

To launch a debug session

Do one of the following:


    • Right-click a JCL member in Project Explorer and select Debug As and select the desired debug configuration.

    • Right-click a JCL member in the Host Explorer navigation tree and select Debug As and select the desired debug configuration.

      Important

      The five most recently used debug configurations with the same dataset name and host are available from the Debug As submenu.


    • Right-click a JCL member in the Host Explorer navigation tree and select Debug As>Xpediter IMS MPP Debug Session. The Select Debug Configuration dialog box appears, showing all previous launch configurations of this type that use the JCL member. Select the debug configuration to be run and click Debug.
    • From the Run menu, select Debug Configurations. The Debug Configurations dialog box appears. Select an Xpediter IMS MPP configuration to use for the debug session. Click Debug.

Upon launching an IMS MPP debug session, users are prompted for the user ID and password for the system running the session. After your IMS MPP job is submitted, the message “Waiting for Xpediter debug session…” appears in the Console view, indicating that Xpediter is waiting for the IMS MPP transaction to be executed. When the IMS MPP transaction has been entered and intercepted by Xpediter, the source for the program displays and the execution pointer stops at the first executable line of code. The tab or the source view displays the load module name and the CSECT name in load module [CSECT] format.

Important

If Skip All Breakpoints has been selected on the Breakpoints View toolbar, a message appears to give the user an opportunity to change this setting.


Important

The user ID and password for a given system are stored in memory for that system as long as Topaz Workbench is running. When they are closed, user IDs and passwords are released from memory.

Important

When a debug session is prepared, the source of the target program displays with the execution pointer stopped at the first line of executable code.

Views in an IMS MPP session

  • The Console view shows the current status of the debug session. For instance, messages display when attempting to connect to the mainframe, upon connection, and when the job specified in the debug launch configuration is submitted.
  • The Debug view provides information about the debug session as well as controls for forwarding progress of the debug session.
  • The Memory view displays the values in memory and allows users to edit them during a debug session.
  • The Open DDIO view allows users to browse source listing files and set breakpoints during a debug session.
  • The Variables view allows users to view and edit variable names, types, and values during a debug session.

To run multiple IMS MPP transactions

Xpediter/Eclipse allows multiple IMS MPP transactions to be run for any transaction criteria that is specified on the Target tab.

When the IMS MPP Transaction Complete dialog box appears at the end of testing the current transaction, do either of the following:

  • Click Yes if you want to run another transaction. The debug session remains active so you can execute another IMS transaction.
  • Click No if you do not want to run another transaction. The Xpediter/IMS log displays (if enabled on the Launch Configuration Log tab), the debugging session terminates (as shown in the Console view), and the IMS MPP batch region terminates.

Important

It is possible (but not advised) to terminate the IMS MPP debugging session by selecting the launch configuration or transaction thread and clicking icon_debug_view_toolbar_terminate.gif. If this is done, Xpediter/IMS is unable to terminate the batch IMS MPP region and Xpediter/Eclipse issues a warning. The Console view displays the messages “Xpediter/IMS is unable to stop the IMS MPP batch region. Please use IMS to stop the IMS MPP batch region”. To test another IMS MPP transaction using Xpediter/Eclipse, the batch IMS MPP region must manually be stopped, via IMS.

Displaying the Xpediter Log

The Log tab in an IMS MPP launch configuration contains an option to display the log at the end of each debug session. When this option is enabled, the log appears when the debug session terminates, and the Console tab displays a message signaling the end of your session.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*