Opswise Controller 5.2.0 Maintenance
Introduction
Stonebranch provides product maintenance in the form of updated product installation packages. This document lists the product installation package maintenance history for Opswise Controller 5.2.0.
Note
You only can install a maintenance package to a product installation of the same version, release, and modification levels (see #Versioning, below).
For example, you can install a 5.2.0.3 maintenance package to a 5.2.0.x installation, but you cannot install a 5.2.0.3 maintenance package to a 5.1.0.x installation.
Exception for Opswise Controller 5.2.0 only
You can use the 5.2.0.x maintenance release of Opswise Controller to apply maintenance to any Opswise Controller 5.1.1.x release. You do not have to perform an upgrade.
Product Packaging
A package maintenance level is incremented when the package changes or the package installation changes.
Stonebranch changes product version, release, or modification identifiers at its discretion when it deems an appropriate number of enhancements or capabilities have been introduced to warrant the change.
Versioning
Package version numbers are comprised of four numeric identifiers: version, release, modification level, and maintenance level.
For example, for Opswise Controller 5.2.0.0:
5 = Version 5
2 = Release 2
0 = Modification Level 0
0 = Maintenance Level 0
Packaging Methods
The Opswise Controller 5.2.0 packages are provided in formats appropriate for the target platforms.
See Installation, Upgrade, and Applying Maintenance for information on installing, upgrading, and applying maintenance to the Opswise Controller.
Package Maintenance Levels
This section identifies the changes included in Opswise Controller 5.2.0.
Release 5.2.0.5 - January xx, 2015
Change ID | Description |
|---|---|
B-04698 | Change to Time Triggers using date adjustments to avoid skipping scheduled time if they are re-enabled (see also D-05426). |
D-04906 | Enabling an interval time trigger with restricted start time > end time does not schedule the trigger for the current day. |
D-05118 | Enabled trigger fires on same day of removed Custom Day from list of dates. |
D-05414 | Timer for enabled Trigger is not canceled if Calendar/Custom Day update results in Trigger not having a next scheduled time. |
D-05415 | Time Trigger with Date Adjustment = Plus skips qualifying times. |
D-05416 | "Ops.OMS.Input.Msg.Processor" warning about "startTransaction called when already in a transaction." |
D-05418 | Time Trigger with Date Adjustment = Less does not resolve next scheduled time when Adjustment Amount > 1. |
D-05426 | Time Trigger with Date Adjustment = Plus may skip if the trigger is automatically re-enabled due to change in Trigger or Calendar. |
D-05446 | Time Trigger with Date Qualifier = Custom Period and Date Adjustment = Less skips the current period. |
D-05447 | Time Trigger with Date Adjective = 1st and Date Noun = list of Custom Days does not work beyond current year. |
D-05464 | Do Not Trigger restriction not working for Time Trigger with Date Adjustment. |
Release 5.2.0.4 - December 2, 2014
Change ID | Description |
|---|---|
D-05308 | Resources not returned if task instances skipped due to "Runtime" run criteria. |
D-04936 | Workflow remains in Running/Problems status after problem jobs have been Finished. |
D-05363 | Workflow stuck in Running status and Workflow Monitor showing tasks with no status after purge on MySQL. |
Release 5.2.0.3 - June 30, 2014
Change ID | Description |
|---|---|
B-03436 | Validate New Jobname field in z/OS task. |
B-04363 | Add ability to auto-retry based on specific exit codes. |
B-04364 | Auto clean-up for override JCL library. |
B-04539 | Add ability to turn off workflow task instance permission inheritance. |
B-04562 | Add property to truncate member names in the z/OS task JCL reference to eight characters. |
B-04566 | Add unique index on ops_exec table to improve workflow task instance performance. |
D-04040 | Trigger Skip Count should not be restored from previous version. |
D-04384 | Workflow remains in Running status when the last task is aborted. |
D-04446 | Cannot resume passive node when Start Server Paused Opswise Property is set to true. |
D-04453 | OMS servers are not marked disconnected when Controller starts up paused. |