, a toolbar
icon, to get the Version, Build ID, and Copyright information.The ClearPath OS 2200 IDE for Eclipse™ software extends Eclipse software to provide an Integrated Development Environment (IDE) for building OS 2200 applications. Rather than automatically building application code, you can specify the command stream to be used to build the application. This allows you to use existing, new, or customized processes to build the application.
The OS 2200 IDE for Eclipse supports IPv6 and IPv4 networks. This means that OS 2200 IDE for Eclipse recognizes both the IPv6 and IPv4 addresses and translates them into the appropriate binary code for COMAPI. You have to run OS 2200 IDE for Eclipse on a Windows 7 platform.
Click , a toolbar
icon, to get the Version, Build ID, and Copyright information.
Log files are created containing information that is useful in diagnosing problems you might encounter while using the product.
The configuration file for the Unisys Eclipse Logging plug-in is located in <eclipse>/plugins/com.unisys.logging.core/logger.properties. One of the purposes of the configuration file is to control the amount of information included in the log file. If you encounter an error, support personnel might ask you to make a simple change in the configuration to include more detailed diagnostic information in the log.
Errors and warnings are written to the Windows Event Log. Errors, warnings, and other internal status information are written to a log file located in <workspace-directory>/.metadata/.plugins/com.unisys.tde.core/unisys-ca.log.
If you encounter an error while using the product, support personnel might ask you to send them a copy of the log file.
Although the development process can vary, the typical development phases are as follows.
Phase |
Description |
1 |
Retrieve archived code elements and place them in a program file in the OS 2200 environment. This program file is referred to in the Eclipse IDE as the work file. |
2 |
Modify the code in the work file using the Eclipse IDE. |
3 |
Build the code using the appropriate process. |
4 |
Test the code. |
5 |
When the code is ready, place the new version in the archive. |
The OS 2200 IDE for Eclipse traditional development environment plug-in provides state-of-the-art editing and automated builds during the modify and build phases of development.
An OS 2200 Eclipse project is a view of a work file located in the OS 2200 environment. The elements in the work file are seen as links in the Eclipse project. These links are aliases for the OS 2200 elements in the work file. The link includes
The file name, reflecting the OS 2200 element
An extension, signifying its type
The type indicates either the kind of code module it is or the editor to be used to update the element. For example, an element type of COB produces the extension COB, which indicates a COBOL code module.
When you edit and save code using the Eclipse IDE, the changes are saved to the OS 2200 code element in the work file. Only the elements with which you wish to work in the Eclipse IDE need links in the OS 2200 project. You can create new elements and delete elements in the work file using the Eclipse IDE.
The OS 2200 Eclipse project uses the build process defined by the user. You can call ECL streams and SSG skeletons that already exist for an application, or you can create a new or modified command stream to perform the builds. During the build process, the commands in the build stream and the output are placed in the OS 2200 console view (an Eclipse view).
An Eclipse perspective is a combination of views, menu items, and toolbar items designed to accomplish specific development activities such as code editing, debugging, and testing. The OS 2200 project is an Eclipse perspective that is geared to development in the OS 2200 environment. It includes a navigation view with a list of the links to the work file elements and has toolbar buttons for commands that are unique to OS 2200 development.
The UCS interactive debugger operates by causing the OM or ZOOM to call back to the PC from which you are doing the debugging during the normal run of the OM or ZOOM. The executable must be static linked to include certain OMs and cause PADS to be called through a special entry point. The OM or ZOOM acts as a TCP/IP client, and the PC acts as the listener. The OS 2200 system must be configured to allow calling out, and firewalls must not prevent a PC from receiving connection requests from the OS 2200 system.
The following operating considerations apply to interactive debugging:
Debugging is supported only for statically linked OMs, not for dynamically linked OMs.
Debugging is not supported for programs that change COMAPI registration.
Debugging HVTIP is not supported.