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.

Enabling Debugging Across Multiple-LPARs in a CICSPlex

Related topics

Customizing-after-installation

Executing a Program Containing Multiple CSECTs (Code Debug CICS PL/I)

The Code Debug Service Provider requires the Code Debug TP configuration data set (TPCONFIG) to identify all of the other Service Providers, in other LPARs, that are to share CICSPlex information. Code Debug CICS also requires TPCONFIG to identify all the CICS regions that should be contacted by the Batch Interface to CICS NEWCOPY.

This task involves Code Debug CICS Installer.

Configuration Considerations

If your configuration file is on shared DASD that can be accessed by all LPARS, only one data set with one member is required. The structure of entries within a member is such that one member may provide all of the necessary information for all Code Debug Service Providers and the Code Debug CICS Batch Interface to CICS NEWCOPY. However—particularly for the Batch Interface to CICS NEWCOPY—you may find it easier to have multiple members in one data set, or even multiple data sets.

TPCONFIG should have its access security set so that all users can read it, but it can be updated only by those to whom you have granted edit access.

TPCONFIG does not have to be in PDSE format, however a PDSE is recommended to avoid compression issues if you frequently modify the members.

An example of a TPCONFIG member is provided in SMXDSAMP member MBRTPCNF.

Task 17.7 Create and Use TPCONFIG

  1. Edit and submit the sample JCL member JCLTPCNF to allocate TPCONFIG and copy the sample configuration member.
  2. Customize TPCONFIG to your installation needs.

Task 17.8 Specify Service Provider Communication Parameters

The Code Debug Service Provider uses TCP to communicate to other Service Providers. Within the XDSSPROC JCL:

  1. Specify the TPCONFIG data set name in the TPCONFIG DD statement.
  2. Specify the TPCONFIG member in the MEMBER parameter.
  3. Specify the Port Number for this instance of the Service Provider in the PORT parameter.
  4. Add an entry to the TPCONFIG member for each instance of the Service Provider that should be connected. For an example XDSS entry, see SMXDSAMP member CFGXDSS.

Important

Your TCP Systems Programmer can provide you with a Port Number and either a Domain Name or an IP Address for each instance of the Service Provider that you create.


Warning

The Code Debug Service Provider can be executed as a started task or as a batch job. If the Service Provider is started during the IPL process and gains control before TCP/IP has started, then the TCP link between Service Providers will not be established automatically, and an error message (XSP3002E DBUGTCP cannot locate TCP/IP) will be written to the Service Provider JESLOG. If this scenario occurs, you can issue Operator Command INITTCP to manually establish the TCP link between Service Providers after TCP/IP has been started.

 

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