List and Retrieve Batch Link Jobs

Use the Batch Link Queue feature to list and retrieve batch link jobs. Select from the list the jobs that you want to debug.

You can select the following types of jobs for debugging:

• Jobs that are submitted or started on the mainframe but not selected for debugging.

• Jobs that are suspended in the middle of a debugging session.
  The application saves the debug session information so that debugging continues from where it was suspended.

• Jobs that are executing on a different LPAR than the one you are currently logged on to. The following prerequisites apply to debugging a job on a foreign LPAR:

  • The LPAR must be located within the SYSPLEX.

  • A CA InterTest™ server must be running on the LPAR.

  • The SYSPLEX option available in the CAMRSTBZ program must be enabled during configuration.

    Note: For more information about enabling the SYSPLEX (Cross-LPAR) Debugging Feature, see the CA InterTest and SymDump documentation.

Follow these steps:

1. Select CA InterTest™, List Batch Link Queue.
   The Batch Link Queue dialog opens.

2. Select the server connection for which you want to view the batch link jobs in the Servers drop-down box.
   The table lists all suspended jobs for the server connection. If SYSPLEX support is enabled, the table lists all suspended jobs executing within the SYSPLEX.

   Note: If you define a server as default when adding or configuring a server, this server is pre-selected.

3. Select the job you want to debug in the table.

   Note: If you select a job on a foreign LPAR, you must enter credentials for that LPAR. The SYSID column displays the LPAR the job is executing on.

4. Select the project to use for debugging the selected job and click Finish.
   The application begins debugging the selected job.

   Note: When a job is retrieved and a debug session is restarted, the application automatically synchronizes breakpoints with the debugger engine. This allows for occasions where a batch job is retrieved from the mainframe and breakpoints were altered, and then the job was once again suspended. It also allows you to change breakpoints before resuming the debug session.