SAS/C Software: Changes and Enhancements, Release 6.50

Introduction

The remote debugger consists of two cooperating processes with a client/server relationship: the debugger display and control process and the client program process (see Architecture ). The debugger display process can communicate with the client program using IBM's Advanced Program-to-Program Communication (APPC) access method if (and only if) that process is running in a different address space or on a different system.

The debugger display process is the server, and is the inbound side of the APPC conversation. It dynamically registers the debugger's Transaction Program (TP) name through the APPC/MVS Register_Test, Accept_Test, and Get_Conversation service calls. The program being debugged is the client, or outbound side of the APPC conversation, and issues the outbound CPI-C Allocate call to connect to the debugger display.

Currently, the debugger display process supports APPC under MVS only. The client program can run in any environment that supports the SAS/C runtime library and the APPC Common Programming Interface Communications (CPI-C) API. However, APPC can be used as the communication method only when you start the debugger using the independent startup method. You must use the TCP/IP communications access method whenever you start the debugger processes with the automatic startup method.

The APPC setup requirements are different for each environment in which the remote debugger is supported. The following sections describe these requirements.

Chapter Contents
Previous
Next
Top of Page