Two fixes have been recently made available for Tivoli Decision Support for z/OS (TDSz) v1.8.1 users to make component installation easier.
1. APAR PM98548
Prior to this APAR, when installing a new TDSz component or re-installing a TDSz component after applying maintenance, a non-zero return code would be received. In most instances this would be a return code 8.
The vast majority of these RC8 issues during installation were caused by the preprocessor encountering SQL errors. In most cases, these errors indicated only that an SQL statement had failed even when the result of failure was not harmful and in many cases anticipated, so could/should be safely ignored.
The most common reasons for the non zero return code to be generated was due to the following:
a) Trying to alter a table which does not yet exist
b) Trying to add a column when that column already exists
c) Trying to create a table which already exists.
When these above errors were the result of the standard way TDSz makes changes to existing objects which you may, or may not, already have installed in your database, the correct action is to ignore the error message.
APAR PM98548 has changed the way TDSz produces error messages during component installation. After applying PM98548, all components should now install/re-install with a return code of zero. If a non zero return code is received, it is likely to be a more serious error which should be investigated.
2. APAR PI08273
Prior to this APAR, when users attempt to install a component and there is nothing in their &HLQ.LOCAL.DEFS data set, an error message (DRLA071) is displayed despite installation proceeding correctly. After applying PI08273 you will no longer see this error message displayed under this scenario.
Secondly, when installing a component TDSz will perform a check for user modified objects. Currently when this check is performed it will show objects that have been modified by previous APARs as being user modified. The reason for this is because the version of the object was changed from ‘IBM’ to its APAR number (for example, ‘PI08273.V181’) to identify the changes introduced with the APAR. After applying APAR PI08273, these objects will no longer be displayed as being user modified.