RSED integration

Eclipse clients communicate with the host by using the RSED started task of z/OS Explorer, FMID HALGxxx. z/OS® Debugger must make itself known to RSED for its services to become available.

Note:

For z/OS Debugger 16.0 and older releases, the z/OS Debugger features documented here were provided by IBM z/OS Explorer Extensions 16.0 and older, FMID HHOPxxx, in combination with IBM Explorer for z/OS 3.3 and older, FMID HALGxxx.

rse.env, the z/OS Explorer configuration file

The z/OS Explorer RSE server processes (RSE daemon, RSE thread pool, and RSE server) must know that they are extended by z/OS Debugger. Depending on where z/OS Debugger was installed, this detection is automatic, or done through an environment variable in rse.env.

If z/OS Debugger was installed in the plugin/ directory of z/OS Explorer, default /usr/lpp/IBM/zexpl/plugin/, then z/OS Explorer automatically detects the presence of z/OS Debugger on the next restart of the RSED started task, and no further action is required.

If z/OS Debugger was installed in another directory (the default is /usr/lpp/IBM/debug/), then variable RSE_PLUGIN_PATH must be updated in rse.env to specify the install location of z/OS Debugger.

rse.env is located in /etc/zexpl/, unless you specified a different location when you customized and submitted the z/OS Explorer FEK.SFEKSAMP(FEKSETUP) job. You can edit the file with the TSO/E OEDIT command. The syntax of the file follows standard z/OS UNIX shell syntax rules. For example, comments start with a number sign (#) when using a US code page, and spaces around the equal sign (=) are not supported.

Note: For your changes to take effect, the z/OS Explorer RSED started task must be restarted.

#RSE_PLUGIN_PATH=

RSE_PLUGIN_PATH

Reference to plugin products that are not installed in the plugin/ directory. The default is an empty string. Uncomment and change to match the installation paths of products that extend z/OS Explorer. Multiple paths are separated by a colon (:).

Products that are installed in the z/OS Explorer plugin/ sub-directory are detected automatically and do not need to be added to RSE_PLUGIN_PATH.

For example: RSE_PLUGIN_PATH=/usr/lpp/IBM/debug/rse

eqa.env, the environment configuration file

The z/OS Explorer RSE server processes (RSE daemon, RSE thread pool, and RSE server) use the definitions in eqa.env to learn about z/OS Debugger environment variables.

eqa.env must reside in the same directory as rse.env, the z/OS Explorer configuration file, for it to be found. rse.env is located in /etc/zexpl/, unless you specified a different location when you customized and submitted the z/OS Explorer FEK.SFEKSAMP(FEKSETUP) job.

Copy eqa.env from the rse/samples/ directory, default /usr/lpp/IBM/debug/rse/samples/, to /etc/zexpl/ and customize as needed. You can edit the file with the TSO/E OEDIT command.

Default values are provided for all variables that are not explicitly specified. The syntax of the file follows standard z/OS UNIX shell syntax rules. For example, comments start with a number sign (#) when using a US code page, and spaces around the equal sign (=) are not supported.

Note: For your changes to take effect, the z/OS Explorer RSED started task must be restarted.

#EQA_HLQ=${ELAXF_EQA:-EQAW}

#AZU_JES_PROCLIB=SYS1.PROCLIB

#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDISABLE_DBM_INTEGRATION=false"
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddebug.miner.autoreconnect=0"
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddebug.miner.localhost=localhost"

EQA_HLQ

The high-level qualifier used to install z/OS Debugger. The default is EQAW. Uncomment and change to match the location of your z/OS Debugger data sets.

Note: If z/OS Explorer Extensions, FMID HHOPxxx, is also extending the same RSED started task as z/OS Debugger, then z/OS Debugger will use environment variable ELAXF_EQA, if defined, as default value for EQA_HLQ. z/OS Explorer Extensions creates this variable while processing the ELAXF JCL INCLUDE member.

AZU_JES_PROCLIB

Define where cataloged procedures are stored so Early Development Testing (EDT) can analyze them when adding recording parameters to JCL using a cataloged procedure. The default is SYS1.PROCLIB. Uncomment and specify a colon (:) separated list of data sets.

_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDISABLE_DBM_INTEGRATION=false"

Disable integration with Debug Manager, an optional started task of z/OS Debugger. The default is false, which implies that Debug Miner will attempt to connect at least once to Debug Manager. Uncomment and specify true to prevent any attempt to connect to Debug Manager.

_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddebug.miner.autoreconnect=0"

Automatic reconnect to Debug Manager, an optional started task of z/OS Debugger. The default is 0, which implies that, when a connection with the Debug Manager server is not established or lost, the Debug Miner will attempt every minute to reconnect to the Debug Manager. Uncomment and specify a different value to limit how often the Debug Miner will attempt to connect to the Debug Manager.

Table 1. Automatic reconnect to Debug Manager
debug.miner.autoreconnect	Reconnect behavior
-1	Do not reconnect
0 (default)	Attempt to reconnect every minute until successful
1-86400	Attempt to reconnect up to the specified amount of times. The maximum value, 86400, equals 24 hours.

_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddebug.miner.localhost=localhost"

Alternative for the localhost TCP/IP definition. Debug Miner will attempt to connect to the Debug Manager, an optional started task of z/OS Debugger, using the localhost specification. This will fail if localhost does not resolve to the local loopback address (127.0.0.1 for IVPv4, ::1 for IPv6).Uncomment and specify the local loopback address when required.