Default language.

Target tab for Batch

The Target tab of a Batch configuration allows you to define the Batch job location, the job match criteria, the test type, the target system, and the login credentials for your debug session. Multiple steps can be debugged. All fields on this tab are required. The Target tab can be completed using Autofill to automatically populate the job name and steps/programs from the JCL or by entering this information manually.

Note: Multiple-step debugging functionality requires that the HCI and Xpediter/TSO be at the same API level as

Topaz Workbench

. Otherwise only one step will be debugged.

To use Autofill to complete the Target tab for Batch

Autofill allows users to automatically populate the job name and steps/programs from the JCL,

  1. From the Target system group box's Host connection list, select the host connection on which to run the debug session.
  2. From the Login Credentials list, select one of the following:
    • Select Use saved credentials to use the credentials used to log into the selected host.
      note_icon.gifNote: If your site has chosen to disallow stored credentials, this selection has no effect.
    • Select Prompt for login to be prompted to log in when you attempt to launch the debug session on the selected host.

  3. In the Job to Debug group box, specify the dataset and member of the JCL (batch job) that executes the program you want to debug. Click Browse to navigate to the dataset.

    Note

    When the Dataset(member) field is populated, clicking View opens the JCL in a separate window so the user can copy data from it to the Target tab.

  4. Optionally, to override the job name within the JCL member, select the Replace job name check box and enter the new name in the field. When the debug session is launched, the replacement job name is used in a modified version of the JCL.

  5. In the Debug Criteria group box, click Autofill to populate the job name and steps/programs from the JCL. Click here if an error message box appears regarding the JCL containing PROCs.

    Note

    Steps that cannot be debugged do not appear in the Steps/programs box. The Debug Criteria group box lists the criteria of the steps/programs to be debugged. The DB2/IMS column indicates the testing of DB2 batch jobs (using DSN connect) and IMS batch jobs (executing the IMS pre-preprocessor). The Created By column indicates whether the source of the debug criteria is parsed JCL or user-entered.

  6. Click Apply or, when ready to debug, click Debug. The selected step is debugged. If multiple steps were selected for debugging, the first step intercepted is debugged until it ends. At that point, either the next step is intercepted or the batch job terminates and the session ends.

     The LIBRARY keyword of the DSN command (used in DB2 Batch programs that call IKJEFT01 to establish a connection to DB2) is not supported. If your program name is in the library indicated by the LIB keyword, that library must be specified in your JCL JOBLIB, STEPLIB, or in the batch launch configuration Load Libraries tab.
     Click Revert at any time to revert to the last saved state.
     Autofill settings can be exported so they can be shared with others or be imported when configuring a new workspace.

To manually complete the Target tab for Batch

  1. From the Target System group box's Host connection list, select the host connection on which to run the debug session.

  2. From the Login Credentials list, select one of the following:

    • Select Use saved credentials to use the credentials used to log into the selected host.

    note_icon.gifNote: If your site has chosen to disallow stored credentials, this selection has no effect.

    • Select Prompt for login to be prompted to log in when you attempt to launch the debug session on the selected host.

  3. In the Job to Debug group box, specify the dataset and member of the JCL (batch job) that executes the program you want to debug. Click Browse to navigate to the dataset.

    Note

    When the Dataset(member) field is populated, clicking View opens the JCL in a separate window so the user can copy data from it to the Target tab.

  4. Optionally, to override the job name within the JCL member, select the Replace job name check box and enter the new name in the field. When the debug session is launched, the replacement job name is used in a modified version of the JCL

  5. In the Debug Criteria group box, follow the steps below to specify the job name, step name(s), and program name(s) defined in the JCL for the program(s) you want to debug. Multiple steps can be debugged within the session.

    Note

    The Debug Criteria group box lists the criteria of the steps/programs to be debugged. The DB2/IMS column indicates the testing of DB2 batch jobs (using DSN connect) and IMS batch jobs (executing the IMS pre-preprocessor). The Created By column indicates whether the source of the debug criteria is parsed JCL or user-entered.

  6. In the Job name field, specify the job name of the JCL dataset member being submitted. Xpediter uses this job name to intercept this job for testing.

      • Click Add to add a step/program to debug. The Add dialog box appears.
      • In the Step field, specify the name of a step for Xpediter to intercept. If the JCL contains PROCS, the Step field should contain the PROCSTEP to intercept.
      • In the Program field, specify the name of a program for Xpediter intercept.
      • Select one or both of the DB2 or IMS check boxes. The DB2 and IMS check boxes indicate the testing of DB2 batch jobs (using DSN connect) and IMS batch jobs (executing the IMS pre-preprocessor). By default these check boxes are cleared. Since a DB2 DSN batch job typically executes PGM=IKJEFT01 and an IMS batch job usually executes PGM=DFSRRC00, selecting the check boxes instructs Xpediter to intercept these programs and to subsequently debug the program specified in the Program Name field. Further, when either check box is selected, the Program Name field must contain the full name of the application program to be invoked in the DB2 or IMS environment; no generics or wildcards are allowed.
      • Click OK. The criteria is added to the Target tab.
      • Repeat until each step to be debugged appears in the table.

    2. Note

      Any of these fields can be wild-carded, but cannot all be completely wildcarded.

  7. Select or clear the Debug all steps that match the specified criteria check box. Selecting it causes all steps that match the debug criteria to be debugged. Clearing it causes only the step with a check mark to be debugged.

  8. Click Apply or, when ready to debug, click Debug. The selected step is debugged. If multiple steps were selected for debugging, the first step intercepted is debugged until it ends. At that point, either the next step is intercepted or the batch job terminates and the session ends.

    Note

    The LIBRARY keyword of the DSN command (used in DB2 Batch programs that call IKJEFT01 to establish a connection to DB2) is not supported. If your program name is in the library indicated by the LIB keyword, that library must be specified in your JCL JOBLIB, STEPLIB, or in the batch launch configuration Load Libraries tab.
     Click Revert at any time to revert to the last saved state.

To address an error message regarding the JCL containing PROCs

If the JCL contains PROCs but does not specify their location, location information must be specified on the Autofill page of the Preferences dialog box. Before Autofill functionality can be used, follow the appropriate steps below, depending on whether the PROC libraries have previously been added to the preferences.

If the PROC libraries have not previously been added to the preferences

If the PROC libraries have not previously been added to the preferences and a message indicates that the PROC was not found, follow the steps below.

  1. Close the Debug Configurations dialog box.
  2. From the Windows menu, select Preferences>Compuware>Xpediter>Autofill. The Autofill page of the Preferences dialog box appears.

  3. Click Add to open the Add Datasets dialog box on which to type the PROC libraries to be used to resolve the JCL PROCs during the autofill operation. Optionally, do any of the following:

    • Click Browse to open the Dataset Selection dialog box on which to browse for datasets to select for populating the Autofill page.
    • Select a PROC library and click Edit to edit its name.
    • Select a PROC library and click Move Up or Move Down to change its location in the input order.
    • Select a PROC library and click Remove to remove it from the list.

  4. If desired, click Validate to verify that the datasets exist. A failure message appears if validation errors exist. Reasons for validation failure include the following:

    • The dataset is not foun
    • The dataset is migrate
    • The user does not have authority to the datase
  5. Address any validation failures.
  6. Click OK on the Autofill page.
  7. Restart the procedure above for using Autofill to complete the Target tab for Batch.

If the PROC libraries have already been added to the preferences

If the PROC libraries have already been added to the preferences yet a message indicates that autofill validation failed, follow the steps below.

  1. On the Autofill Validation Failed dialog box that appears, click the Configure Proc Libraries for Autofill link. The Autofill page of the Preferences dialog box appears.

  2. Click Add to open the Add Datasets dialog box on which to type the PROC libraries to be used to resolve the JCL PROCs during the autofill operation. Optionally, do any of the following:

    • Click Browse to open the Dataset Selection dialog box on which to browse for datasets to select for populating the Autofill page.
    • Select a PROC library and click Edit to edit its name.
    • Select a PROC library and click Move Up or Move Down to change its location in the input order.
    • Select a PROC library and click Remove to remove it from the list.

  3. If desired, click Validate to verify that the datasets exist. A failure message appears if validation errors exist. Reasons for validation failure include the following:

    • The dataset is not foun
    • The dataset is migrate
    • The user does not have authority to the datase
  4. Address any validation failures.
  5. Click OK on the Autofill page.

  6. On the Autofill Validation Failed dialog box, click one of the following:

    • To retry the autofill operation, click Retry. The Debug Criteria group box populates with the job name and steps/programs from the JCL.
    • To continue with the autofill operation but ignore validation errors, click Continue.
  7. On the Target tab, click Apply or, when ready to debug, click Debug. The selected step is debugged. If multiple steps were selected for debugging, the first step intercepted is debugged until it ends. At that point, either the next step is intercepted or the batch job terminates and the session ends.

To share autofill settings

Autofill settings can be exported so they can be shared with others or be imported when configuring a new workspace.

  1. From the Export Compuware Configuration dialog box, export the autofill settings by selecting Xpediter>Autofill and completing the remainder of the dialog box. Refer to the Topaz Workbench User Guide online help for details on using this dialog box.
  2. From the Import Compuware Configuration dialog box, import the autofill settings by selecting Xpediter>Autofill and completing the remainder of the dialog box. Refer to the Topaz Workbench User Guide online help for details on using this dialog box.

To edit a step/program from the Debug Criteria group box

  1. In the Debug Criteria group box, select the row for the step/program to be edited.
  2. Click Edit. The Edit dialog box appears.
  3. Make the necessary changes and click OK. The changes are reflected on the Target tab.

To remove steps/programs from the Debug Criteria group box

  1. In the Debug Criteria group box, do one of the following:
    • Select the check boxes for any steps to be removed and click Remove.
    • Select Remove All.

The changes are reflected on the Target tab.


 

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