************************************************************************************************* * * * * ClearPath OS 2200 IDE for Eclipse * * * * Version 4.4.1 * * * * Unisys Corporation * * * * Release Date:31-08-15 * ************************************************************************************************* Overview: --------- This build is the major release for 'OS 2200 IDE for Eclipse' for ClearPath 16.0 is identified with the version number 4.4.1 and is being released in two variants of 32-bit and 64-bit. What is new in this release: ---------------------------- This release is based on Eclipse 4.4.1 capabilities and requires J2SE 1.8 to be installed on the Windows workstation. It is capable of building Java 1.5 and higher compliant applications. This release contains major features, such as: 1. Eclipse Migrate from 4.3.2 (Kepler) to 4.4.1 (Luna) 2. Support on Java 8 3. Eclipse Context menu Console View, Breakpoint console and Telnet console 4. Eclipse more flexible project build stream 5. Eclipse enhance OFE to create/delete new workfile/folder 6. Eclipse enhance OFE to create/delete new element 7. Eclipse enhance OFE to have Copy and Paste action for elements 8. Eclipse OFE cache list of qualifiers, filenames, non-standard OS 2200 9. Eclipse clear cache option for cache created by OS 2200 projects 10. Eclipse test the connection configuration 11. Ability to copy the contents from OS 2200 search view An eclipse-2200-4-4-1-150807.zip is available to download. It contains Eclipse 4.4.1 and all recommended plug-ins and this eliminates the need to download and install individual plug-ins to use IDE. Eclipse 32-bit variant will work for Windows 7 IA32 and IA64 architectures. Eclipse 64-bit will work only for Windows 7 IA64 architecture. Based upon the Eclipse variant, the user will have to install JRE 32-bit or 64-bit accordingly. Also, refer to the Best Practices and Limitation document to work with ClearPath OS 2200 IDE for Eclipse. Working with OS 2200 Eclipse IDE -------------------------------- Migrating projects that are created prior to version 3.7.2.A1 build IC1-20140520 -------------------------------------------------------------------------------- Migrating older version of the projects ======================================= Since Eclipse version 3.7.2.A1 build IC1-20140520, Eclipse caches the files into local file system. Because of this, it is not possible to use the same workspace that was created before that version. Hence it is mandatory for a user to create a new workspace. Steps to migrate are as follows: 1. Create a new workspace. 2. Import the project using File->Import. 3. In the import, expand General and select "OS 2200 Import Project". 4. In the import project, select the project which you wish to import. By importing the old projects into the new workspace, Eclipse will migrate the old project to be compatible with the latest version of the project. Note: 1. Workspace created using version 3.7.2.A1 build IC1-20140520 or a later version is compatible with this release. 2. 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. 81205949 The saved element by the Save is invalid 2. 25405039 Host Manager View incorrectly shows connected status ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Supported Platforms: Windows 7 (IA32 and IA64 architectures), Windows 8 (IA32 and IA64 architectures) and Windows 8.1 (IA32 and IA64 architectures) IMPORTANT: The debugger for Eclipse-2200 3.7.2.A1 and above would work only with the new version of pads$lib named as Eclipse2200padslib37.zip (eclipse2200*pads$lib37.). Please install the new version of library and use only that while debugging the UCS programs. The steps to install the pads$lib are mentioned in the installation guide for Eclipse-2200 (47292107-010.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 using Preferences->General->Workspace->New text file line delimiter->Other->Unix. Note that it is applicable for only 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. 3: If you wish to change the character encoding to LetsJ, you can set it in Eclipse preferences. The value is set using Preferences->General->Workspace and select LetsJ for Text file encoding->Other. ---------------------------------------------------------------------------------------------------- **** 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: 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. As a workaround, add the files to the project. 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. 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. 12. 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. 13. While working with the help files, if you encounter Error 500, you may close the help window and re-initiate the help page. 14. 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. 15. When exporting a project, if only a few files are selected , Eclipse will not create a directory of the selected project to be exported, inste Eclipse will copy the selected files only. 16. Eclipse.exe for 64-bit variant will carry the original icon as it could not be modified. 17. Because of Eclipse 4.x.x, the Telnet view is not retained in Debug/OS2200 perspective --------------------------------------------------------------------------------------------------- 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: http://public.support.unisys.com/