DDIO tab


Multiple methods exist for defining the source listing files to be included in the debug session. The simplest way is to set up DDIO rules so DDIO members are automatically found, as described in the Code Debug TSO and Code Debug IMS Installation and Configuration Guide's section about using the run-time parameter CTLASSD. If this is not set up at your site, an error message will indicate that no DDIO was found when the debug session is launched. If that occurs, use one of the following methods to define the source listing to be included in the debug session.

  • Compile the program to be debugged with Common Shared Services 8.6 or later, which places a reference to the DDIO dataset inside of the load module so discovery is automatic. Note, however, that if the DDIO member is promoted to a different DDIO dataset, this pointer is no longer valid. Refer to the Common Shared Services documentation for details.
  • Use the DDIO tab of the Debug Configurations dialog box to define the source listing files to be included in the debug session by browsing for datasets; adding, editing, or removing datasets; and changing the order in which datasets are listed. Datasets are processed in the order in which they appear in the table.

Note

Code Debug does not support Common Shared Services enhanced listings. For information on enhanced listings, refer to the Common Shared Services documentation.



 

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