Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Using the Code Debug TP Configuration File

Related Topics

Assembler User Guide

Code Debug for CICS C User Guide

COBOL User Guide

Code Debug for CICS PL I User Guide

The Code Debug TP configuration file (TPCONFIG) is used by Code Debug CICS for two purposes:

  • To identify Code Debug Service Providers that are to share CICSPlex information
  • To identify all of the CICS regions that should be contacted by the Batch Interface to Code Debug CICS NEWCOPY.

Efficiency Considerations

Technically, each member of the TPCONFIG partitioned dataset may contain entries for all three possible uses mentioned above. This is because each record within a member starts with a record identifier, and records with an identifier for a different purpose are ignored. However, even though it is technically feasible to have all of the information in one member, doing so would be inefficient.

It is possible to lump all Batch NEWCOPY records (NEWC) into one TPCONFIG member, but then each time the Batch Interface to Code Debug CICS NEWCOPY is used, the program will try to contact all CICS regions. The volume of regions contacted could clutter the report produced and extend the Batch Interface’s runtime. In addition, regions that do not contain the program being newcopied would always report errors, increasing the likelihood of other errors being overlooked. Therefore, BMC recommends that logically grouping NEWC entries into members that mirror your site’s program (load library) distribution.

Record Identifiers

Records in an TPCONFIG member with an asterisk in position one are considered comment records and are ignored. Records that have a blank in position one are scanned for a following record identifier.

Service Provider Records

The record identifier for Code Debug Service Provider records is XDSS. Each Code Debug Service Provider that controls any portion of a CICSPlex should have a record in the member that represents that CICSPlex.

Following the XDSS record identifier are:

  • one or more blanks
  • the PORT number for that Service Provider to listen on
  • one or more blanks
  • the IP Address for that Service Provider.

The PORT number should be assigned by your TCP Systems Programmer. If a Domain Name Server is available for GETHOSTBYNAME calls, then the Domain Name may be specified instead of the IP Address.

Batch Interface to Code Debug CICS NEWCOPY Records

The record identifier for the Batch Interface to Code Debug CICS NEWCOPY records is NEWC. Each CICS region that you want to be contacted to attempt NEWCOPY should have a record in the member.

Following the NEWC record identifier are:

  • one or more blanks
  • the transaction ID to be initiated in CICS (XPNC is recommended)
  • one or more blanks
  • the IP Port Number for the CICS region (or keyword EXCI if the EXCI communication method is to be used)
  • one or more blanks
  • the IP Address for the CICS region (or APPLID of the CICS region if the EXCI communication method is to be used).

If a Domain Name Server is available for GETHOSTBYNAME calls, then the Domain Name may be specified instead of the IP Address.

 

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