Starting the DL/I Debug Server on the z/OS® host

On z/OS®, you can configure the debug server to debug IMS™ DLI.

Syntax

You start a debug server by using z/OS® JCL commands. The syntax for the parameters line is as follows:

-p

Specifies the port number (portno) to which the server listens to communicate with the clients. The value should be between 1024 and 65535.

-V

Specifies the verbosity level of the server. You may specify this parameter up to three times (maximum verbosity).

-a

Specifies authentication mode:

0: Server state: A or U (unauthorized). If U, APF-authorized build programs will fail. If you specify a TSO user ID and password, the server ignores them and the build transaction is performed under the access and authority of the user ID assigned to the build server job.

-n

Specifies the number of concurrent debug sessions. The default is 1. Set n equal to the number of concurrent debug sessions you want to allow. Once there are n number of concurrent debug sessions running, the debug server queues any additional requests and submits them on a first come first served basis as other debug sessions are completed. For optimum performance, set n to the same value as q.

-q

Specifies the size of the queue (q) for clients. The default is 10. Each queued client uses a TCP/IP socket. Therefore setting this too high may require more sockets than are available, causing unpredictable results. If the queue is full, subsequent clients are rejected by the server. However, the build client retries the build in that case. For optimum performance, set n to the same value as q

-t

Starts the tracing of this server job and writes output to STDOUT. This parameter is normally used only for debugging.

Procedure

Modify the proxy job JCL to match your system configuration.

The JCL to start a proxy on the host is contained in the file named EZEDBGPX.JCL. You must modify the STEPLIB portion of the JCL to match your system configuration. Ensure that the PDS that contains the DRA startup table that you generated (see Creating the DRA Startup Table) is in included in the STEPLIB.

//jobcard
//RUNPGM   EXEC PGM=EZEDBPXY,DYNAMNBR=30,TIME=NOLIMIT,
// PARM='&PARM ,7,0000,,0,,N,0,T,IVP7,,N,,,N'
//* Avoid changing the PARM statement. The &PARM keyword will
//* be replaced by parameters.
//STEPLIB  DD DISP=SHR,DSN=ELA.V6R0M1.SELALMD
//         DD DISP=SHR,DSN=ELA.V6R0M1.SELADBGL
//         DD DISP=SHR,DSN=IMS.SDFSRESL
//         DD DISP=SHR,DSN=IMS.PGMLIB
//         DD DISP=SHR,DSN=CEE.SCEERUN
//DFSRESLB DD DISP=SHR,DSN=IMS.SDFSRESL
//IMS      DD DISP=SHR,DSN=IMS.PSBLIB
//         DD DISP=SHR,DSN=IMS.DBDLIB
//IEFRDER  DD DUMMY
//DFSVSAMP DD DISP=SHR,DSN=ELA.V6R0M1.ELASAMP(ELAVSAMP)
//*
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//CCUBLOG  DD SYSOUT=*

To start a z/OS® debug server, complete the following steps with the ELADBGRN.JCL:

Add a job card.
Modify the STEPLIB, DFSRESLB, and IMS DD statements to point to the data sets that contains the build server load modules and your IMS™ environment. This library contains all the load modules that make up the remote build server.
Modify the ELADBGP DD statement to point to the data set that contains the JCL to run an individual debug proxy job.
Modify the parameter (PARM=) statement as appropriate for your job (see example below).
Submit the job.

Example

The following sample JCL starts the debug server as a batch program for IMS™ debugging:

//jobcard
//*------------------------------------------------------
//RUNPGM   EXEC PGM=ELAMAIN,REGION=7400K,
// PARM='-p 5527 -a 0 -n 10 '
//STEPLIB  DD DSN=ELA.V6R0M1.SELALMD,DISP=SHR
//ELADBGP  DD DISP=SHR,DSN=ELA.V6R0M1.SELAJCL(ELADBGPX)
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//CCUBLOG  DD SYSOUT=*

Special considerations for debugging

If you start the server on z/OS® from an APF-authorized library (this is optional in mode 0), the build script can specify an APF authorized program as the executable.

Note:

In this case, the build script can also specify non-APF authorized programs. However, in a multistep JCL script, an authorized program cannot be run after an unauthorized program.

If the server is not started from an APF-authorized library, the build script can specify only non-APF authorized programs as executables.

Setting the language of messages returned from the build server

The debug server on z/OS® returns messages in any of the languages listed in the next table. English is the default.


Language	Code
Brazilian Portugese	ptb
Chinese, simplified	chs
Chinese, traditional	cht
English, USA	enu
French	fra
German	deu
Italian	ita
Japanese	jpn
Korean	kor
Spanish	esp

To cause debug-server messages to be returned in a language other than English, change the setting of environment variable CCU_LANG on the client machine. The variable contains one of the language codes listed in the previous table. For example, to return messages in French, set CCU_LANG to fra.

Also, the components that invoke the build server may need to issue messages if communication with the build server fails. To return those messages in a language other than English, change the setting of the environment variable CCU_CATALOG on the client machine. The value of CCU_CATALOG is a string like the following (on a single line):

  shared_resources\eclipse\plugins
  \com.ibm.etools.egl.distributedbuild_version\executables\ccu.cat.xxx

shared_resources: The shared resources directory for your product, such as C:\Program Files\IBM\SDP70Shared on a Windows™ system or /opt/IBM/SDP70Shared on a Linux™ system. If you installed and kept a previous version of an IBM® product containing EGL before installing your current product, you may need to specify the shared resources directory that was set up in the earlier installation.
version: The installed version of the plugin. If more than one is present, use the one with the most recent version number, unless you have a reason to use an older version.

xxx: The code for the language of interest; one of the codes listed in the previous table