Using Xtend with the Debugger

To use Xtend while debugging, you define a Janus Web Server port and an APSY subsystem in the Online, as well as configuring the Xtend GUI and the Debugger Client on your workstation. Once this is complete, you can use Xtend with the Debugger, as described above in Using a local editor.

You must use version 2.11 or higher of Xtend. The details provided below are for version 2.11 using Janus Web Server.

The configuration steps below are described in this section. They assume the Debugger installation has been completed and tested, as described in Product Installation. The Xtend product installation and setup is also documented in greater detail in Help files provided with the product.

1. Install and configure Xtend in your Model 204 Online
2. Install and configure the Xtend GUI
3. Update the Client configuration file
4. Test the configuration

Install and configure Xtend in your Online

Skip to the next subsection (Install and configure the Xtend GUI) if Xtend is already installed at your site.

1. Download to your workstation two Xtend installation files (one for the Xtend GUI and one for the Model 204 subsystem and web port). 2. Set up a Model 204 subsystem (XTEND) to control Xtend processing.

Notes for doing this are provided in the XtendInstall.HLP file in the XtendInstall folder. See the "Xtend Apsy" section.

3. From the PC, run the Xtend installer executable (XtendInstall.exe), which will populate the XTEND subsystem files. 4. In the Online, run the XTEND.JANUS.DEFINE procedure in the XTENDPRC procedure file to start the Xtend Janus Web port.

The default port number for the non_SSL port is 7878; for the secure port it is 7879. Change these numbers if necessary for your site.

Install and configure the Xtend GUI

1. If you will use Janus Debugger and have configured a proxy server for the Internet Explorer browser, update the proxy settings to provide a bypass for connections to the Xtend web port.
   1. From the <var">Tools menu, select <var">Internet Options; then select the <var">Connections tab, and click the <var">LAN Settings button.
   2. Locate the <var">Proxy Server area, and click the <var">Advanced button.
   3. In the <var">Exceptions area, in the list box labeled "Do not use proxy server for addresses beginning with," specify the URL of the Xtend web server port you defined.
   4. Click <var">OK as needed to close the multiple dialog boxes.
2. Set up a remote connection to Model 204 from the Xtend GUI.
   1. Open the Xtend GUI executable file (Xtend.exe), and select <var">Options</vavr> from the <var">View menu.
   2. In the <var">Options dialog box, select the <var">Remote tab.
   3. In the grid in the main work area, specify a name for this connection and supply a Model 204 user ID, host name, and the web server port you defined, and click the <var">Apply button.
   4. If you will use TN3270 Debugger, select the name (Caption) of the remote connection you just defined from the Default edit online when using TN3270 Debugger drop down list, then click the <var">OK button.
   5. Optionally, review and update the settings in the other <var">Options tabs.
3. Add the names of the procedure files (and their privileges) whose procedures you will be editing with Xtend.  
4. Select <var">Administrator Functions from the <var">Admin menu; then select the <var">Files tab.
   1. In the <var">File columns, name the procedure files that contain the procedures you want to make accessible from Xtend; in the <var">Privileges column, select a privilege level.
   2. This information can alternatively be specified in the XTEND subsystem itself.
   3. Click the <var">Save Details button, followed by the <var">Close button.

Note: For procedure files that have explicit passwords, you must either add the file name to the XTEND subsystem files listed in the Subsystem File Use screen in the Model 204 Subsystem Management facility, or you must modify a subroutine in the XTENDPRC procedure file (as described in the XtendInstall.HLP file).

1. Test your connection.
   1. In the <var">Procedure List dialog box, select the tab that is labeled with the name of your remote connection.

A list of your procedures is retrieved and displayed.

1. 1. Display a test procedure's code (double click the procedure name), make some update, then save the updated procedure by clicking the Save File icon on the toolbar.
   2. In your Online, check that the updated procedure has replaced the original.
   3. If your connection test is successful, close Xtend.

Update the Debugger Client configuration file

Once Xtend is installed and configured for debugging, you enable the Debugger(s) to invoke it by adding an entry to the Debugger Client configuration file (debuggerConfig.xml). This file is installed in the same directory as the Debugger Client executable file, and it is initially configured as part of the Debugger Client installation.

To update the file:

1. Open the debuggerConfig.xml file in a text editor.
2. Add an <editor> element (bounded by an <editor> start tag and an <\editor> end tag) at the same level (as a sibling of) the existing <serverList> element.

Include these <editor> subelements, and specify values for them as described in the Comment section below:

Subelement

Comment

<program></program>

The identifier of the Xtend program executable file (case does not matter). For example: <program>xtend</program>. Note: If the Windows system variable Path does not include the folder path that points to the Xtend executable (for example, C:\Program Files\Xtend), either add it to the Windows variable now, or specify the folder path before the executable file name in the <program> value. To locate the Path variable specification on a Windows 7 workstation, find the Control Panel (say, Start menu > Settings > Control Panel), then select System > System advanced settings > Advanced tab > Environment Variables button > System variables > Path, then click Edit to see the full specification of the Path variable.

When complete, your configuration file should have a structure like the following:

<debuggerConfig version="1.0">    <serverList>        .        .        .    </serverList>    <proxy>        .        .        .    </proxy>    <editor>       <program>xtend</program>    </editor>        .        .        . </debuggerConfig> 

3. Save and close the file.

Test the configuration

In the Debugger Client, edit a procedure. 1. Restart the Debugger Client. 2. Load a procedure in the <var">Source Code tab of the Debugger Client:

• Janus Debugger: From your web browser, invoke a URL that includes a procedure.
• TN3270 Debugger: Issue the TN3270 DEBUG ON command; then include a procedure from the Model 204 command line.

3. Right click a line of code, select <var">Line Information from the context menu, then click the <var">Edit button on the pop up that opens.

Xtend should open, displaying in its working area the procedure that contains the code line that you right clicked. If it fails to do so, and you verified earlier that, by itself, Xtend successfully transfers files from the Model 204 Online, begin your troubleshooting in the Debugger Client debuggerConfig.xml file settings for the <editor> element.