************************************************************************************************* * * * ClearPath OS 2200 IDE for Eclipse * * * * Version 4.7.0.1 * * * * Unisys Corporation * * * * Release Date: 15-12-17 * ************************************************************************************************* Overview: ========= This build is "4.7.0 IC1" release for 'OS 2200 IDE for Eclipse' for ClearPath 17.0 is identified with the Eclipse version number 4.7.0 and is being released in two variants of 32-bit and 64-bit. ************************************************************************************ IMPORTANT NOTICE ************************************************************************************ It is mandatory to follow the section "Migrating projects that are created prior to version 3.7.2.A1 build IC1-20140520" to avoid high MIPS usage. What is new in this release: ============================ 1. NFS:39827201 - NON PROJECT OFE DATA FILES SLOW EDIT Issues that have been addressed in this build. # UCF Description of the issue ----------------------------------------------------------------------------------- 1. 81296472 Incorrect Detail View 2. 39478838 OS 2200 Properties screen should fit on screen An eclipse-2200-4-7-0-171201.zip and eclipse-2200-4-7-0-171201-X64.zip are available to download. It contains Eclipse 4.7.0 and all recommended plug-ins. This eliminates the need to download and install individual plug-ins to use IDE. Eclipse 32-bit variant works for Windows IA32 and IA64 architectures. Eclipse 64-bit works only for windows IA64 architecture. Based on the Eclipse variant, the user must 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 ================================ Use "OS 2200 Import Project" functionality to import projects to OS 2200 workspace. 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 to the local file system. Because of this, it is not possible to use the earlier workspace. So, it is mandatory for a user to create a new workspace. If the number of projects or the number of elements in the projects are high, create a new project using the current version of OS 2200 Eclipse IDE. If the number of projects are less than 10 and the number of elements in each project are less than 300, perform the following steps to migrate the projects: 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 migrates 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 must be closed and re-opened to see the correct colors. However, the heap size may increase by around 5 MB. 3. In data explorer all columns in a table are listed in "reverse order", to re-arrange you must use "-Djava.util.Arrays.useLegacyMergeSort=true" without quotes in eclipse.ini file after -vmargs. After modifying the Eclipse.ini file, it is recommended to restart OS 2200 Eclipse. It is observed that Symantec Endpoint Protection (SEP) issuing a warning and quarantining the eclipse.exe while launching the OS 2200 Eclipse. Use one of the following options to remediate the issue: 1. On the SEP warning window select “Allow this file” option to retain exlipse.exe; or 2. If eclipse.exe has been quarantined, it can be restored by opening, Symantec Endpoint Protection -> View Quarantine -> Select eclipse.exe -> Select Restore option -> Click ‘OK’ on confirm restore window. Supported Platforms: Windows 7 (IA32 and IA64 architectures), Windows 8 (IA32 and IA64 architectures), Windows 8.1 (IA32 and IA64 architectures) and Windows 10 (IA32 and IA64 architectures) IMPORTANT: The debugger for eclipse-2200-4-6-0 and above works only with the new version of pads$lib named as Eclipse2200padslib46.zip (eclipse2200*pads$lib46.). Please install the new version of library and use 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). 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. To change it to spaces, go to Preferences -> General -> Editors -> Text Editors -> Insert spaces for tabs. 3. To change the character encoding to LetsJ, go to Preferences -> General -> Workspace and select LetsJ for Text file encoding -> Other. 4. After installing the ca update site in Eclipse v4.7, start Eclipse using the following command for the first time to complete the OS 2200 plugin installation. /eclipse –clean 5. It is observed that including the plugin “Dali Java Persistence Tools - EclipseLink JPA Support” results in displaying the context menu items incorrectly. This is applicable if Eclipse JEE version 4.6 onwards is downloaded from the Eclipse website directly. To rectify this issue, uninstall “Dali Java Persistence Tools -EclipseLink JPA Support” plugin. Perform the following steps to uninstall the plugin: Go to, Help -> Installation Details Selected the “Dali Java Persistence Tools - EclipseLink JPA Support” under Installed Software, click Uninstall button and Restart the Eclipse. -------------------------------------------------------------------------------------------------------------- Known issues with Eclipse ========================== 1. If you are unable to view the OS 2200 Menu in the OS 2200 perspective, reset the perspective. To reset navigate to Window -> Perspective -> Reset Perspective. In case you wish to update the existing Eclipse, it is highly recommended to restart Eclipse-2200 after the update process. 2. Generate build stream will not work with project(s) containing element(s) without extension. 3. When the OS 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 continues to use the existing password for any CIFS connections until the user changes the password through TIP/Demand. 4. When the user has specified a breakpoint file name in the BRKPT files tab, Eclipse builder appends @PRT,I ECL to the start the build stream. If the network is down while executing this ECL, Eclipse-2200 may freeze. 5. 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 message dialog as "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 type the following command: net use / /delete For example, net use \\os2200host.unisys.com\os2200 /delete 6. If the user chooses to open a COBOL/C/H file by using the Open File feature, the outline view may not display the contents. As a workaround, add the files to the project. 7. 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. 8. While running low on memory, an attempt 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. 9. After importing a project, it may not update the project or the element status properly. Perform "Sync->Update Project Status" from them project context menu to update the status correctly. 10. When exporting a project, if few files are selected, Eclipse will not create a directory of the selected project to be exported, instead Eclipse will copy the selected files only. 11. The Telnet view is not retained between Debug/OS2200 perspectives in Eclipse v4.x. 12a. If an external compare/merge tool such as Windiff is used on the elements that are not downloaded into the cache folder then the comparison/merge operation is unknown. As a workaround, download the element and then use the compare/ merge feature. 12b. During compare/merge operation, for performance benefit, host copy is downloaded to a temporary location. Therefore, merge must be performed to the local element. If default Eclipse compare/merge utility is used, do not perform 'Copy All Non-Conflicting Changes from Left (cache) to Right (host)' operation. 13. The field size of COMP-1 and COMP-2 are calculated as 2 bytes instead of 1. It will be rectified in a future release. 14. It is observed that on a lower resolution or small monitors, certain dialogs/wizards are not displayed correctly. Even some message description is truncated in “sync element(s) with host” dialog due to fixed size dialog. However, there is no impact on the behavior. 15. As part of the SR 29522364, OS 200 IDE for Eclipse issues a command, set 34359738367 in order to read a data file successfully. Issuing this commands modifies the last modified timestamp on the data file. Hence, the IDE includes a modified marker in the OS 2200 Project Explorer for such a file. 16. When user clicks the COPY PROC name then the PROC is opened. If user navigates back to the COBOL program, then the selection remains on PROC name until the user clicks in the editor. 17. Using old (previous released) workspace, for uninitialized element user will not get an option to download in sync scenarios. As a workaround, double click the element to download and open. 18. If the file/element is deleted on the host the information message is displayed to the user when the user performs 'sync from local to host'. This is different compared to the information message displayed when user performs save/saveall operation for same file/element. 19. Intermittently, if an element is saved after performing merge operation, a dialog, "File has changed outside of this compare editor. What do you want to do?” is displayed. If you cancel the dialog, then element cannot be modified in the merge editor, but it can be saved successfully. 20. After restarting Eclipse, if a project already exists and the elements are already open then the Link With editor will not work. As a workaround user must expand the existing project. 21. For the first time, rename throw exception dialog while renaming local project folder. 22. DMU view is preferred to open in OS 2200 perspective. If the user has opened the DMU view in any other perspective make sure that it is closed and then open it in OS 2200 perspective. 23. In DMU, REDEFINES fields are not displayed in the data file view. In the tree view the fields with group level OCCURS (multidimensional array) is shown as a single string blob in the current version. 24. If you select Window -> Preferences -> Fortran, Problem Occurred error dialog appears and preferences page will not load. A bug has been raised against Eclipse, ref https://bugs.eclipse.org/bugs/show_bug.cgi?id=520139 ---------------------------------------------------------------------- Documentation: For documentation on how to use this IDE, see the help contents of IDE. This documentation is improved and expanded since the last release. You may also choose to review the most current documentation on our support site: https://public.support.unisys.com/