Configuration of an Code Debug Launch Configuration from a Fix Request Import


Users can import a performance problem fix request file that was exported from iStrobe or an abend fix request file that was exported from Abend-AID. From this imported fix request file, a Code Debug launch configuration can be created. Once the Code Debug launch configuration artifact is created, additional configuration is required to make the configuration usable in Code Debug.

Important

Refer to the BMC-AMI-DevX-Workbench-for-Eclipse-User-Guide help for information on importing a fix request. Refer to the iStrobe online help for information on exporting a fix request from iStrobe. Refer to the Abend-AID Web Browser Interface help for information on exporting a fix request from Abend-AID.

To complete the configuration of a Code Debug launch configuration created by importing a fix request

  1. After importing a fix request to create a Code Debug launch configuration, launch Code Debug.
  2. Click debug_exc.gif and select Debug Configurations. The Debug Configurations dialog box appears.
  3. Select the launch configuration created by importing the fix request. The Common tab appears. This tab allows users to specify where to save the launch configuration and displays comments about the launch configuration.
  4. Under Save to, specify where to save the launch configuration by selecting Default location, which saves it to the workspace, or by selecting Project and then entering or browsing to the desired location.
  5. Click the Target tab and fill out any required fields. Required fields are indicated by messages at the top of the tab and vary by launch configuration type. Refer to the BMC-AMI-DevX-Workbench-for-Eclipse-User-Guide help for information on configuring host connections, if necessary.
  6. For batch, DB2 stored procedures, and IMS MPP launch configurations, click the DDIO tab and add the DDIO files if they were not prepopulated by the fix request file. Refer to the appropriate help topic for the DDIO tab.
  7. Click Debug. The debug session begins.

 

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