If you accessed this document from a product or documentation media, you may not be reading the latest Release Notes . For the most recent information, go to FrontLine , Compuware’s customer support website. The first time you access FrontLine, you are required to register and obtain a password. After logging onto FrontLine, select your product from the drop-down list and click Go. On the left side of the page, click the Documentation link. You will find the latest Release Notes listed with the other product documentation.
ISPW is a modern, end-to-end Agile source code management, release automation, and deployment automation tool that enables mainframe application developers at all skill levels to fulfill business requirements, optimize code quality, and improve developer productivity through mainframe DevOps.
Enhanced functionality to collect ISPW usage data and provide records to Enterprise Common Components to upload for use and analysis by zAdviser. zAdviser can then measure quality, velocity, and efficiency of Mainframe development. Refer to the Enterprise Common Components Advanced Configuration Guide for Release 17.02 for detailed instructions on how to enable the creation of zAdviser records.
• Topaz CLI for ISPW now supports downloading of specific Set, Assignment, or Release containers as well as downloading of changes (instead of complete download) on subsequent runs of the downloading process.
• The new ISPW Guided Configuration dialog lets you follow the installation steps on a screen with the JCL generated for you. This provides a clearer view of the steps and where you are with the JCL built from your input.
Java OutOfMemory errors may occur when editing a large file or displaying a large JES report. These errors can often be avoided by increasing the maximum size of the JVM memory heap. The initialization files in Topaz Workbench or Eclipse (topaz.ini or eclipse.ini) include an Xmx parameter (default 512m or 1024m) used to specify the maximum heap size. The optimum value for this parameter varies depending on the OS used, memory fragmentation, and other factors.
On 32-bit Windows, the theoretical heap size is limited to 2GB due to how Windows allocates memory, but this is reduced by many factors. Generally, the stated maximum is 1536m, while a commonly stated max range is 1200m to 1500m. The optimal setting for a particular installation--with no OutOfMemory errors or noticeable garbage collection pauses--can only be determined by experimenting with different values. Compuware recommends increasing the Xmx value to 1200m as a starting point and increasing or decreasing the value in small increments, such as 512m, until an optimum value is found. However, even with a setting of 1536m, large JES output can easily exceed that value. The only practical solution in such situations is to install the products on a 64-bit OS.
On 64-bit Windows operating systems, heap size is limited by your Windows virtual memory specification, minus a small amount of memory used by the OS and other processes. Specifying 4GB or more for the Xmx parameter can be practical depending on the Windows virtual memory size.