Target tab for DB2 SP

The Target tab of a DB2 Stored Procedure configuration defines the location of the Application Environment WorkLoad Manager (WLM) JCL, DB2 stored procedure filter criteria, and the target system for the debug session.

To complete the Target tab for DB2 SP

1. In the Target System section, specify the host connection on which to run your debug session.
2. In the Login Credentials section, do one of the following:
   

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

     Warning

     Note

     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 Application Environment (WLM JCL) section, specify the dataset, job name, member, and step name of the JCL (Batch job) that creates the WorkLoad Manager (WLM) address space. If the JCL contains PROCS, then the Step name field should contain the PROCSTEP of the program that initiates the WorkLoad Manager address space. Optionally, 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 DB2 Stored Procedure Filter Criteria section, specify the filter criteria for the DB2 stored procedure to be debugged:
   • In the Program name field, specify the name of the program you want to debug. This name matches the name of the listing found in the Compuware listing file specified in the DDIO tab.
   • In the Schema name field, specify the schema name associated with the stored procedure. Xpediter uses this name along with the stored procedure name to resolve the WorkLoad Manager (WLM) application environment and the load module name. The site's DB2 administrator or system support responsible for WLM should provide the schema and stored procedure names that have been defined to WLM and DB2. Beginning with DB2 8.1, the schema name can be up to 128 bytes long.

   • In the Stored procedure name field, specify the stored procedure name associated with the schema name. Xpediter uses the name to resolve the WorkLoad Manager (WLM) application environment and the load module name. The site's DB2 administrator or system support responsible for WLM should provide the stored procedure's name that has been defined to WLM and DB2. Beginning with DB2 8.1, the stored procedure name can be up to 128 bytes long.

     Warning

     Note

     To intercept a trigger that calls a DB2 stored procedure, specify the stored procedure here. To debug a user-defined function (UDF), specify the FUNCTION name (not the SPECIFIC name).

   • In the Client End User ID/PC Account Code/IP Address field, specify one of the following:

     • The user ID of the client (caller of the stored procedure)
     • The account code used by the middleware (or batch job)
     • The client's IP address (which is applicable if the requester is not a DB2 subsystem)
     • An asterisk * (which indicates a generic wildcard match; only the subsystem and stored procedure name will be used for interception)

     This field cannot be blank. If this field as entered does not match the client's user ID, the account code, or IP address, and an asterisk was not entered, Xpediter will not intercept the stored procedure. If the client is CICS, enter the AUTH from the CICS DFHRCT.

   • In the DB2 subsystem name field, specify the name of the DB2 subsystem where the stored procedure is defined.

   • In the Maximum number of tests field, specify how many times the stored procedure will be intercepted.

     Warning

     Note

     During a test, a user can terminate the WLM address space, which will override this value and cause immediate termination of the test. To accomplish this, in the Debug view, click the configuration name and click the terminate icon.