Target tab for IMS MPP

The Target tab of an IMS MPP debug configuration allows you to define the location of your IMS MPP JCL, the IMS program and transaction code, and the target system for your debug session.

To complete the Target tab for IMS MPP

1. In the Target system section's Host connection field, specify the host connection on which to run your debug session.
2. In the Login credentials field, do one of the following:
   

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

     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 IMS MPP JCL section's Dataset(member) field, specify the dataset and member of the IMS MPP JCL (batch job) that creates the IMS MPP address space. Optionally click Browse to navigate to the dataset.

   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 section's Job name field, specify the job name of the JCL dataset member being submitted here. This job name will be used by Code Debug IMS to intercept this job for testing. This field cannot be wildcarded.
6. In the Step name field, specify the name of the step for Code Debug to intercept. If the JCL contains PROCS, then the Step name field should contain the PROCSTEP to intercept. This is a required field and it may be wild carded.
7. In the IMS User ID field, specify the IMS Userid that will be used to test this program/transaction. This field is used to specify the ID of the IMS user issuing the IMS transaction you want to debug and is applicable only if IMS user ID or the IMS DATA Value Driven Intercept support is enabled. A single character asterisk (*) in this field indicates a generic match (any User ID will be considered a match). This field defaults to a single asterisk (*).
8. In the Programs/transactions table, click Add. The Add dialog box appears.
9. In the Program field, specify the IMS MPP program to be tested using Code Debug IMS. This field cannot be wildcarded.
10. In the Transaction field, specify the IMS MPP transaction to be tested using Code Debug IMS. This field cannot be wildcarded.
11. In the Data field, optionally specify the IMS MPP data to be used by the program/transaction specified above. This field can be used in conjunction with the User ID field (if the IMS DATA Value Driven Intercept has been installed) to further restrict the selection of transactions to those that contain the specified data in the transaction buffer.
12. Click OK. The program/transaction information is added to the Target tab.

13. Click Add to add additional programs/transactions and repeat as necessary.

    Note

    Multiple entries in the table with the same transaction code are disallowed (program and data fields can be duplicated).

    Note

    To edit the program, transaction, or data information, click Edit to open the Edit dialog box. To remove a program/transaction, select it from the table and click Remove. To remove all programs/transactions in the table, click Remove All.

14. In the Options section, select the Hogan test check box if you want to set a flag for Code Debug IMS to perform a Hogan test.