Default language.

Xpediter CICS Launch Configurations


To create a new Xpediter CICS launch configuration

  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

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

  2. In the left pane, select Xpediter CICS 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 CICS Debug Session root node.

    Important

    Alternatively, you can share launch configurations by copying the files from one workspace to another.

  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:

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 a debug session

  1. From the Run menu, select Debug Configurations. The Debug Configurations dialog box appears.
  2. Select the configuration listed under the particular type of debug session.
  3. Click Debug. The Debug button is disabled when a selected configuration contains invalid data .

To launch a debug session

  1. From the Run menu, select Debug Configurations. The Debug Configurations dialog box appears.
  2. Select a CICS configuration to use for the debug session.
  3. Click Debug. Upon launching a CICS debug session, users are prompted for the user ID and password for the region running the session. When a debug session begins, a source view of the target program defined in the load module of the launch configuration is shown.


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.
  • The user ID and password for a given region are stored in memory for that system as long as Eclipse is running. When Eclipse is closed, user IDs and passwords are released from memory.
  • 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.
  • Unlike a Batch debug session, execution begins upon the launch of a CICS session. The transaction that executes the program to be debugged must be executed by an appropriate means outside of Xpediter/Eclipse. Once executed, Xpediter/Eclipse traps the transaction and debugging begins.

Views in a CICS session

  • The Console view shows the current status of the debug session (such as messages when attempting to connect to the mainframe and when the debug session ends).
  • The CICS Channels and Containers view allows users to view a list of channels and containers, as well as to preview and browse data, when debugging a CICS transaction that involves container data
  • The Debug view provides information about the debug session as well as controls for forwarding progress of the debug session.
  • The CICS-Traps-view provides information about the current trap criteria set for the active CICS 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.

 

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