Code Debug Batch Launch Configurations

To create a Code Debug Batch launch configuration from Code Debug

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 Code Debug Batch Session ) and their corresponding configurations.

   Note

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

2. In the left pane, select Code Debug Batch Session.

3. Click  or right-click the node and select New. A child node representing the newly created configuration is added to the Code Debug Batch Session root node.

   Note

   Alternatively, you can share launch configurations by exporting from one workspace and importing them 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 BMC-AMI-DevX-Code-Insights-and-Runtime-Visualizer-User-Guide.)
   • Code Coverage (Optional)
   • Scripting (Optional)
   • Load Libraries (Optional)
   • DDIO (Optional)
   • Log (Optional)
   • Work Files (Optional)
   • Common tab

To create a Code Debug Batch launch configuration from Host Explorer or Project Explorer

1. Do any of the following:

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

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

   Note: 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.

   Note: If the parse is unsuccessful, the data is not populated.
   Note: 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 BMC-AMI-DevX-Code-Insights-and-Runtime-Visualizer-User-Guide)
   • Code Coverage (Optional)
   • Scripting (Optional)
   • Load Libraries (Optional)
   • DDIO (Optional)
   • Log (Optional)
   • Work Files (Optional)
   • Common tab

Note: 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. Do any of the following:

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

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

   Note: 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 Code Debug 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.

  Note

  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>Code Debug Batch 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 a batch configuration to use for the debug session. Click Debug.

The debug session runs.

Views in a Batch 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 (Batch 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 Debug view provides information about the debug session as well as controls for forwarding the progress of the debug session.
• The Variables view allows users to view and edit variable names, types, and values during a debug session.

Displaying the Xpediter Log

The Log tab in a Batch 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 to debug session terminates and the Console tab displays a message signaling the end of your session.