************************************************************************************************* * * * ClearPath OS 2200 IDE for Eclipse * * * * Version 4.6.0 * * * * Unisys Corporation * * * * Release Date:30-09-16 * ************************************************************************************************* Overview: --------- This build is the major release for 'OS 2200 IDE for Eclipse' for ClearPath 17.0 is identified with the version number 4.6.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: ---------------------------- This release is based on Eclipse 4.6.0 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.4.1 (Luna) to 4.6.0 (Neon) 2. Eclipse wizard to generate TIP RA Buffer Helper Classes 3. Tips and Tricks at start-up 4. Open Element/File in Eclipse in read only mode 5. Reduce the setup for debugging the programs 6. TDATE$ ER Calls Search through OS 2200 Eclipse Search 7. Up folder-cursor move back to the parent directory 8. Option to list Project files in modify date order 9. OS 2200 RDMS Configuration Wizard 10. OS 2200 Eclipse Search performance improvement 11. Qualification on Windows 10 Issues that have been addressed in this build. # UCF Description of the issue ----------------------------------------------------------------------------------- 1. 32593581 Unable to create elements in lower case. 2. 81231940 The element name is invalid on File explorer. 3. 37094128 DISP-2 are incorrectly sized in feild size feature 4. 36292169 TRUNCATION OF FILE 5. 37564735 Error lines not highlighted (ACOB/PROC/Unique shares) 6. 37606818 Working Connection test fails! 7. 36754751 Field size shows wrong size for some COMP fields 8. 35362115 PADS FAIL DUE TO TIMEOUT An eclipse-2200-4-6-0-160920.zip and eclipse-2200-4-6-0-160920-X64.zip are available to download. It contains Eclipse 4.6.0 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 IA32 and IA64 architectures. Eclipse 64-bit will work only for Windows 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 -------------------------------- Use "OS 2200 Import Project" functionality in order to import projects into OS 2200 workspace. If the number of projects or the number of elements in the projects are high, create a new project using this version of 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. If the number of projects are less than 10 and the number of elements in each of the project are less than 300, steps to migrate the projects 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. 3. In data explorer all column in a table is listed in "reverse order", to make it in proper order user need to append "-Djava.util.Arrays.useLegacyMergeSort=true" without quotes in eclipse.ini file after -vmargs. After modifing the Eclipse.ini file, it is recomended to restart OS 2200 eclipse once. 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 would work only with the new version of pads$lib named as Eclipse2200padslib46.zip (eclipse2200*pads$lib46.). 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. When exporting a project, if only a 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. 14. The 64-bit Eclipse.exe retains the original icon. 15. The Telnet view is not retained in Debug/OS2200 perspective in Eclipse v4.x. it will rectify in feature release. 16. If an external compare tool such as Windiff is used on the elements that are not downloaded into the cache folder then the comparison is in deterministic. As a workaround, download the element before using the compare feature. 17. 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. 18. It is observed that on a lower resolution and or lower monitor sizes, certain dialogs/wizards are not displayed correctly. However, there is no impact on the behavior. 19. If only a single editor is opened in read-only mode and make it writable or "Reload" function is used on the only editor, it will not display the status bar. By clicking on any other view (e.g., OS 2200 File Explorer), the workbench will be restored. Hence, the status bar will be visible. 20. As part of the SR 29522364, OS 200 IDE for Eclipse issues a command, set 34359738367 in order to get 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. 21. This is applicable if Eclipse Neon JEE is downloaded from the Eclipse website directly. It has been observed that including the plugin “Dali Java Persistence Tools - EclipseLink JPA Support” causes the context menu items display incorrectly. Please uninstall “Dali Java Persistence Tools - EclipseLink JPA Support” plugin to rectify this issue. Steps to uninstall the plugin are as follows. Go to, Help -> Installation Details Selected the “Dali Java Persistence Tools - EclipseLink JPA Support “ under Installed Software , click Uninstall button and Restart the Eclipse. 22. The plugin which provides the recording feature (PracticallyMacro) is under review by the Unisys Legal team. It will be made available subject to Legal approval. Until such time, record and playback functionality within OS 2200 Eclipse IDE will not be available. --------------------------------------------------------------------------------------------------- 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: https://public.support.unisys.com/