************************************************************************************************* * * * Clear Path OS 2200 IDE for Eclipse * * * * Version 3.7.2.A2 * * * * Unisys Corporation * * * * Release Date:25-08-14* ************************************************************************************************* Overview: This build is an IC build for Eclipse IDE on OS 2200 on the major release CP 15.0. This build is identified with the version number 3.7.2.A2. ------------------------------------------------------------------------------------------------- This release is based on Eclipse 3.7.2 capabilities and requires J2SE 1.6 or higher to be installed on the Windows workstation. It is capable of building Java 1.5 and higher compliant applications. An eclipse-2200-all-in-one-3-7-2-A2-20140822.zip is now available on the FTP-site. It contains Eclipse 3.7.2 and all recommended plug-ins and this eliminates the need to download and install individual plug-ins to use IDE. Working with OS 2200 Eclipse IDE -------------------------------- The version 3.7.2.A1 build IC1-20140520, incorporates major changes in terms of architecture. Local cache has been introduced in this release. Because of this, it is not possible to use the same workspace that was created before this Build. Hence it is mandatory for a user to create a new workspace. Then onwards, the old projects that have been created from an earlier release can be migrated using import mechanism. Importing projects: a. While importing contents into OS 2200 project, please choose “OS 2200 Import Project” option from File -> Import option. b. While importing contents into Java project (E.g., RA project), please choose “Existing Project into Workspace” option from File -> Import option. By importing the old projects into the new workspace, eclipse will migrate the old project to be compatible with the lastet version of the project. Note: Workspace created using version 3.7.2.A1 build IC1-20140520 is compatible with this release. There are associated CIFS parameter and runstream changes that each client should consider. Refer to the Best Practices and Limitation document for more information on this topic. F4 provides a shortcut for color coding of user variables, section names, and paragraph names. The colors can be defined in the COBOL Preferences. Note that as new code is typed in the COBOL editor, it is displayed as the default color. The COBOL editor needs to be closed and reopened to see the correct colors. However, the heap size may increase by around 5 MB. Issues that have been addressed in this build. # UCF Description of the issue ------------------------------------------------------------------------------------------------- 1 81101957 Element names not treated properly by eclipse 2 81081344 Opening an element will delete the list of errors in problems view 3 81079528 Eclipse allowing user to rename/type modification of element when it is in open state 4 81059781 Auto generate build option is not adding the element to the runstream 5 81057044 Eclipse listing the Problems entries to wrong elements 6 81055912 Eclipse allows creation of project over Private files 7 81055211 Save As operation is not working as expected 8 81053499 Eclipse closes while building the project 9 81051941 Generate build stream will not list the compiler statement for some elements 10 81043078 selecting switch to duplex command line in telnet logs an error 11 25586488 Element Date/Time changes on copy from Eclipse 12 29786355 Eclipse - log & error dialogue box 13 80886420 During dragging and dropping an element between projects the default element name is being taken which is greater than 12 characters. 14 80886411 An element name (name with space or special characters) is being copied successfully from one project to other when dragged and dropped. Supported Platforms: Windows 7 (IA32-bit and Intel® 64-bit architectures) NOTE: 1. On a 64-bit operating system, Eclipse IDE will run as WoW64 bit application. Use a 32-bit version of Java Runtime Environment (JRE) v1.5 or higher. 2. If users have used Eclipse-2200 3.7.0 version (major release or its ICs) or 3.7.2 version (only the major release), then they may have to follow the steps outlined later here. However, users who already have Eclipse-2200 3.7.2 and above may not require to perform these steps. I. The user has to delete the old host-accounts and login-accounts before starting with Eclipse-2200 3.7.2 and above. To do so, perform the following steps: 1. Navigate to C:\Users\\AppData\Local\Unisys\os2200\ide 2. Delete the HostAccount.xml and LoginAccount.xml files. II. The user may have to delete any existing mapped network drives. 1. Open Windows Explorer, navigate to the Tools menu and select Disconnect Network Drive . . .. The Disconnect Network Drive window opens. 2. Select the drives with "NONE" as the name and then click OK. III. Restart Eclipse-2200 IMPORTANT: The debugger for Eclipse-2200 3.7.2.1 and above works only with the new version of pads$lib, named as Eclipse2200padslib37.zip (eclipse2200*pads$lib37). Install the new version of library and use it only while debugging the UCS programs. The steps to install the pads$lib are mentioned in the installation guide for Eclipse-2200 (47292107-005.pdf). ---------------------------------------------------------------------------------------------------- Eclipse workspace settings ========================== 1: By default, the new line character in the editor is set as Carriage Return (\r) Line Feed (\n). If you wish to change the default to Line Feed (\n), you can set it in Eclipse preferences. The value is set by using Preferences-> General-> Workspace-> New text file line delimiter-> Other-> Unix. Note that it is applicable only for the new files that are created henceforth. 2: By default, the Tab character (Ascii \t) is used when Tab is pressed in the editor. If you wish to change it to spaces, you can set it in Eclipse preferences. The value is set using Preferences->General->Editors->Text Editors->Insert spaces for tabs. ---------------------------------------------------------------------------------------------------- Installation ========= Eclipse IDE requires Scite editor to open large files. Scite is bundled as part of an all-in-one package. However, if the Eclipse 2200 CA plug-in is installed from the update site, then Scite is not installed in the Eclipse package. Under such an instance, you must manually download and install Scite. Perform the following steps to install Scite: 1. Go to the Unisys Eclipse all-in-one download site at ftp://ftp.support.unisys.com/pub/2200/IDE/Eclipse-2200-3-7-2-A/ 2. Download the Scite.zip to the c:\temp folder. 3. Using Windows Explorer, browse to the c:\temp folder. 4. Unzip Scite.zip to folder. For example, if Eclipse is installed under c:\EclipseIndigo32Bit, then unzip Scite.zip to c:\EclipseIndigo32Bit. **** Known Issues with Eclipse : **** 1. Due to a fairly severe bug in Eclipse, DO NOT refactor/rename your OS 2200 project name while in the Java perspective. However, it is fine to do so in the OS 2200 perspective. Renaming the OS 2200 project in the Java perspective will delete the contents of the work file on the 2200 and the files will become local to your workspace. To track this Eclipse issue, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=163232 When an Eclipse fix is available, Unisys will repackage the all-in-one package. 2. If in the OS 2200 perspective you do not get to see the OS2200 Menu, try to reset the perspective. You can reset it by navigating to Window -> Reset Perspective. In case you wish to update the existing eclipse, it is highly recommended to restart eclipse-2200 after the update process. 3. Generate build stream will not work with Project(s) containing element(s) with no extension. 4. The Rename of Project dialog will not show the error (element already exists) if the text is entered in lowercase. The error message will be shown once the user clicks on the OK button. 5. When the 2200 Userid password is set to expired, OS 2200 does not action this until the next TIP/Demand login. As such, CIFS connections using the existing password are allowed until the user changes the password through TIP/Demand. Therefore, Eclipse will continue to use the existing password for any CIFS connections until the user changes the password through TIP/Demand. 6. When the user has specified a breakpoint file name in the BRKPT files tab, eclipse builder appends @PRT,I ECL to the start of the build stream. If the network goes down while executing this ECL, Eclipse-2200 may freeze. 7. If the data files are updated outside CIFS (for example, through telnet), CIFSUT does not show an update timestamp/content for that data file. The editor may not show the updated editor contents. 8. While working with Eclipse-2200 connection, if Eclipse suggests the user to restart the IDE because of error 1219 and the user restarts Eclipse, there may be a window stating Eclipse failed to disconnect the host. Disconnect the host manually and restart Eclipse. To disconnect the host manually, perform the following steps: On Windows 7: Open the Command prompt, and issue the following command: net use / /delete For example, net use \\os2200host.unisys.com\os2200 /delete 9. If the user chooses to open a COBOL/C/H file by using the Open File feature, the outline view may not show any contents. 10. When a project is imported into the existing workspace, or when closing a project and reopening it after restarting Eclipse, the file name and the elements within the file remain empty. As a workaround, restart Eclipse. 11. In the File Compare dialog, if the user has invoked the File browse dialog to choose the Compare utility or to choose a comparison file, then clicking any other application will send Eclipse into the background. When Eclipse is brought back to foreground, it will become inoperable because of the active File dialog. As a workaround, press Alt+Tab to bring the File Browse dialog to foreground, instead of clicking Eclipse from the toolbar. 12. While running low on memory, an attempt made to open large COBOL files from "Problem View" may result into Eclipse throwing the "OutOfMemoryException" message. This issue is generated from Core Eclipse and the Unisys Plugin for Eclipse 2200 has no control over intercepting this condition. 13. After importing a project, it may not update the project/element status properly. Performing "Sync->Update Project Status" from the project context menu will update the status correctly. 14. While working with the help files, if you encounter Error 500, you may close the help window and re-initiate the help page. 15. When Eclipse is in offline mode, the Close-All option saves the unsaved contents to the cache. However, no message dialog pops up informing the user that the element is not saved to the Host. 16. When exporting a project, if partial files are selected to be open, Eclipse will not create a directory of the selected project to be imported, rather Eclipse will copy the selected files only. 17. Unable to compare datafiles from OS 2200 File Explorer. It is observed that it fails to compare datafiles directly from OS 2200 File Explorer. As a workaround, manually browse and select the datafiles from the Compare dialog. 18. Unable to import projects when one of the project's connection information is unavailable/deleted from Eclipse. It is observed that while importing multiple projects if one of the project's connection information is unavailable or deleted from Eclipse, then it will not import all the other valid projects as well. As a workaround, import projects individually. --------------------------------------------------------------------------------------------------- Documentation: For documentation on how to use this IDE, see the help contents of IDE. This documentation has been improved and expanded since the last release. You may also choose to review the most current documentation on our support site at: http://public.support.unisys.com/