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.
Webhook notifications can now be setup for ISPW. Webhooks can communicate information on ISPW activities such as generate, promote, regress, deploy and fallback to other DevOps tools in real time. Webhooks can be triggered regardless of whether developers or operators use Topaz, 3270 or REST APIs.
The web component of ISPW now use the Compuware Host Communications Interface (HCI) for communication to ISPW. The ISPW web login dialogs will now prompt users for the Host Connection they wish to use. Personal Access Tokens used for ISPW’s REST API have also been updated to a Host Connection.
• Applying this maintenance will affect how the product communicates with Topaz Workbench. This needs to be coordinated with applying the July maintenance for Topaz Workbench. Implementing single signon was done with a shift to HCI. HCI also needs to be updated.
• When used together, ISPW Eclipse and ISPW must be on the same release level to enable single signon. If your site intends to use ISPW in Topaz Workbench, Compuware recommends that you install the latest version of ISPW before installing the latest version of ISPW Eclipse.
• Generate: Provides a way to leverage the ISPW Generate process to do your compile and link. It can be used to perform the Generate operation on Tasks in an Assignment. When processing is complete, you can view the status indicating the success or failure of the compiles.
• Get Information about an Assignment: Retrieves the Application, Stream, Description, Owner, and the customizable WorkRef Number. Additionally, information about Tasks contained in the Assignment can be retrieved, such as the status of Generate operations on each Task in an Assignment.
A set of new REST APIs have been made available to enable integrations with products such as XebiaLabs XL Release. These APIs make it easy to leverage ISPW Deploy in conjunction with existing release management infrastructure using Jenkins, HipChat, and Slack. The initial delivery includes APIs for Create Release, Get Release Information, Promote Release, Deploy Release, and Get Set Information.
A new Web Interface for Deploy is now available to join the existing Approval Interface. You will be able to see the current status of your Releases and even see a graphical representation of what is being deployed and where.
Knowing the potential impact of a change is key; knowing right when you start is critical. ISPW Eclipse now provides for visualization of the impact. Impacts can be generated from source, copybooks, and JCL. For a program, it would show the target calls, what calls it, and the jobs it is in--not only the programs but also where each of those assets are in the development cycle will be obvious in the chart. Adding the visual element provides an easier, more intuitive way to spot dependencies that can affect a project. The chart can be saved as a jpg, png or pdf. The Impact Table can now be saved as a csv.
In ISPW Eclipse, if the Impact Analysis shows other programs might need to be changed, users can now select Program Analysis and get an in-depth view of their program. When editing programs, users will be able to view the structure, code flaws, logic and data flows. CES and a license for Topaz for Program Analysis are required to enable this functionality.
New to ISPW Eclipse is the ability to synchronize compiler errors to a SlickEdit edit session. Clicking an error in the Problems view positions the source code to the line of code that has produced the compile error. Users can quickly size up errors from the compile and go right to the affected lines to see them in context.
Building on the existing Web Approval interface, Compuware now offers a mobile interface suitable for a mobile browser. This enables approvals to be done when away from the office; perfect for critical fixes that need to get into production.
The ISPW Deploy feature has always supported the usage of warehouses on non-z//OS platforms for staging of deployments to open systems. However, Compuware has now extended the warehouse capability so that, when such open system components are checked in or imported to ISPW, they can now be stored in place and managed by an ISPW remote server on any supported platform.
The Software and Hardware Requirements section of the Release Notes has been standardized across all Compuware Mainframe products and their Distributed components. Please note that any versions of third-party software that are no longer supported by their vendors under standard published contracts have been removed from the Software and Hardware Requirements section and placed in the Discontinued Support section of the release notes. However, any third-party software that was supported when this Compuware product went GA will continue to be supported until this product release has reached its End of Support date. No functionality has been removed from the product.
For further information about IBM System z software and hardware compatibility--specifically regarding IBM's z/OS Recommended Service Upgrade, IBM's Extended Address Volumes, IBM DB2 for z/OS, and z/OS product compatibility--refer to http://frontline.compuware.com/charts/hardware.aspx .
For specific required PTFs, consult the Product Currency Tables at https://frontline.compuware.com/apps/oscharts/zos.aspx .
For more information, see Configuring Memory Settings for ISPW Eclipse below.
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.
The product installation package does not include the product documentation. The following ISPW documentation is available in electronic format on the product documentation site at Compuware’s FrontLine customer support website, https://go.compuware.com .
Access the ISPW documentation on the FrontLine documentation site at https://go.compuware.com .
View and print the PDF files with Adobe Reader version 6.0 or more current. Download a free copy of the reader from Adobe’s website, http://www.adobe.com .
Compuware creates a PDX file for each release of every mainframe product. The file is available in ZIP format on FrontLine, Compuware’s customer support website, along with this README and a folder containing two data files. By pre-cataloging the content of the product’s PDFs, the PDX file allows you to quickly search across the entire documentation set without having to search each PDF individually.
1. Go to FrontLine ( https://go.compuware.com ) and navigate to the Documentation page for the desired product.
Your search results will appear almost instantly, grouped by document. Each document with results can be expanded to show a list of matches, with each match including a brief sample of the context in which it occurred. Every match is hyperlinked to the specific page in the PDF where it was found, enabling you to quickly locate the information you’re looking for.
For your convenience, Compuware also provides the ISPW manuals in the Hypertext Markup Language (HTML) format. View HTML files with any standard web browser. Click the icon in the HTML column on the selected FrontLine Documentation page.
You can access online information for Compuware products via our FrontLine customer support website at https://go.compuware.com .
Compuware FrontLine provides access to critical information about your Compuware products. You can review frequently asked questions, read or download documentation, access product fixes, or e-mail your questions or comments. The first time you access Compuware FrontLine, you are required to register and obtain a password. Registration is free.
• All other countries: Contact your local Compuware office. Contact information is available at https://go.compuware.com .
You can report issues via the Quick Link Create & View Support Cases on the Compuware FrontLine home page.
To access Compuware’s site on the Web, go to http://www.compuware.com .