The interactive debugging facility requires that a TCP/IP or CPI-C connection be set up between the workstation and the target system. The interactive debugger setup differs for CICS Transaction Server and IMS or MVS users; however, the workstation setup is the same regardless of your target environment.
The setup of the interactive debugger can be done using either the TCP/IP or CPI-C protocol.
To use the interactive debug facility with TCP/IP you do not need to complete special steps to set up TCP/IP for the development and target environments. However, you must include the interactive debug TCP/IP feature in the passive image. To enable the interactive debug facility through TCP/IP for packaged workstation images, change the workstation address specification to point to the TCP/IP address of your machine. You can do this during packaging. See Specifying the workstation address on the target environment using CPI-C or TCP/IP and Packaging a Smalltalk image for more information.
Your communication product must be set up to allow incoming session allocations. You must define the interactive debug transaction program.
If your program encounters a Smalltalk error while running in the target system, this transaction program definition allows the system to establish a connection with the workstation. See Starting the interactive debugger for information on how to open an XD Debugger window using that connection.
The transaction program you define will open the interactive debugger in an already active Smalltalk session.
Specify the transaction program with the following values:
TP Name: ABTDBGS PIP Allowed: No Conversation Type: Mapped Synchronization level: Any Conversation Security Required: No Operation Type: Queued TP
The TP Name must match the transaction program name used in the CPI-C side information of the client.
Follow your communications software setup for configuring transaction programs.
TP NAME (ABTDBGS) PIP_ALLOWED(NO) FILESPEC(XD_Debugger) CONVERSATION_TYPE(MAPPED) CONV_SECURITY_RQD(NO) SYNC_LEVEL(NONE) TP_OPERATION(QUEUED_OPERATOR_STARTED) PROGRAM_TYPE(BACKGROUND) INCOMING_ALLOCATE_QUEUE_DEPTH(255) INCOMING_ALLOCATE_TIMEOUT(20) RECEIVE_ALLOCATE_TIMEOUT(0);
The values INCOMING_ALLOCATE_TIMEOUT and RECEIVE_ALLOCATE_TIMEOUT cannot be accessed through the interactive facility; you must modify these values using a text editor.
SET APPCTPN=ABTDBGS
CICS users can choose to specify this variable in the CICSENV.CMD file when starting Smalltalk as a CICS transaction.
To setup the CICS Transaction Server environment, you must define and install a partner, a connection, and a session. You can set up the interactive debugger to start on any workstation to which your application running in CICS Transaction Server can access. To ensure that the interactive debugger starts on your own workstation, you must provide your workstation information. The following steps describe how to define and install these:
CEDA DEF PARTN(MYNETID) GR(SMTALK)
The following screen appears. Use the FQ_CP_NAME specification from your Communication Manager configuration file to insert the correct NETName and NETWork options.
DEFINE_LOCAL_CP FQ_CP_NAME(USIBMNR.NRIEYJ00 )
Specify ABTDBGS for the Tpname.
DEFINE PARTN OVERTYPE TO MODIFY CEDA DEFine PARTNer( ) PARTNer ==> MYNETID Group ==> SMTALK Description ==> PARTNER DEFINITION FOR INTERACTIVE DEBUG REMOTE LU NAME NETName ==> NRIEYJ00 NETWork ==> USIBMNR SESSION PROPERTIES Profile ==> DFHCICSA REMOTE TP NAME Tpname ==> ABTDBGS ==> Xtpname ==> ==> ==>
CEDA INS PARTN(MYNETID) GR(SMTALK)
The following screen appears. The partner definition has been installed.
INS PARTN(MYNETID) GR(SMTALK) OVERTYPE TO MODIFY CEDA Install Connection ==> File ==> Lsrpool ==> Mapset ==> PARTItionset ==> PARTNer ==> MYNETID PROFile ==> PROGram ==> TErminal ==> TRANClass ==> TRANSaction ==> TYpeterm ==> Group ==> SMTALK
CEDA DEF CONN(USR1) GR(SMTALK)
The following screen appears. Enter the Netname used in the partner definition.
DEF CONN(USR1) GR(SMTALK) OVERTYPE TO MODIFY CEDA DEFine Connection( USR1 ) Connection : USR1 Group : SMTALK DEscription ==> Connection to MYNETID PS/2 CONNECTION IDENTIFIERS Netname ==> NRIEYJ00 INDsys ==> REMOTE ATTRIBUTES REMOTESYSTem ==> REMOTEName ==> REMOTESYSNet ==> CONNECTION PROPERTIES ACcessmethod ==> Vtam Vtam | IRc | INdirect | Xm PRotocol ==> Appc Appc | Lu61 | Exci Conntype ==> Generic | Specific SInglesess ==> No No | Yes DAtastream ==> User User | 3270 | SCs | STrfield | Lms RECordformat ==> U U | Vb
CEDA DEF SESS(USR1SESS) GR(SMTALK)
The following screen appears. Specify the connection as USR1 and the mode name as #INTER.
DEF SESS(USR1SESS) GR(SMTALK) OVERTYPE TO MODIFY CEDA DEFine Sessions( USR1SESS ) Sessions ==> USR1SESS Group ==> SMTALK DEscription ==> SESSION FOR CONNECTION USR1 SESSION IDENTIFIERS Connection ==> USR1 SESSName ==> NETnameq ==> MOdename ==> #INTER SESSION PROPERTIES Protocol ==> Appc Appc | Lu61 | Exci MAximum ==> 001 , 000 0-999 RECEIVEPfx ==> RECEIVECount ==> 1-999 SENDPfx ==> SENDCount ==> 1-999 SENDSize ==> 04096 1-30720 RECEIVESize ==> 04096 1-30720
CEDA INS GR(SMTALK)
To set up the IMS or MVS environment, you must define a CPI-C destination name as a single name alias representing a combination of a remote LU and a transaction program name. APPC/MVS side information supplies destination information such as the name of the partner program and the name of the LU partner's node. CPI-C provides a way to use system-defined values for these required fields; these system-defined values are called side information. You can set up the interactive debugger to start on any workstation to which your application running in IMS or MVS can access. To ensure that the interactive debugger starts on your own workstation, you must provide the correct side information. The following steps describe how to define the CPI-C destination name using side information:
//STEP1 EXEC PGM=ATBSDFMU //*------------------------------------ //SYSPRINT DD SYSOUT=* //SYSSDLIB DD DSN=SYS1.APPCSI,DISP=SHR //SYSSDOUT DD SYSOUT=* //SYSIN DD DATA,DLM=XX SIADD DESTNAME(destname) TPNAME(ABTDBGS) MODENAME(#INTER) PARTNER_LU(network.lu)
This section covers how to set up the interactive debugger to work against images packaged to run in a workstation environment.
CPI-C users must define a CPI-C destination name as a single name alias representing a combination of a remote LU and a transaction program name.
CPI-C provides a way to use system-defined values for these required fields; these system-defined values are called side information. Add a CPI-C side information statement with a symbolic destination name that matches the workstation address specified when packaging the Smalltalk image, and add a TP_NAME of ABTDBGS.
If you are using the interactive debug facility on a workstation and set up the environment with CPI-C, you must also perform the steps for setting up the workstation environment specified in Specifying the workstation address on the target environment using CPI-C or TCP/IP.
To specify the workstation address so you can use the interactive debugger, do the following: