Hotfix 8 for TIBCO Object Service Broker for z/OS 5.0.0 is now available.
Article ID: KB0105351
Updated On:
| Products | Versions |
|---|---|
| TIBCO Object Service Broker for z/OS | - |
| Not Applicable | - |
Description
Description:
Issues Corrected by Hotfix 8:
=============================
=====================================================================
Product Name: TIBCO(R) Object Service Broker for z/OS
Release Version: 5.0.0_hotfix08
Release Date: July 2009
======================================================================
Introduction
Hotfixes are cumulative. This hotfix includes all previous hotfixes for TIBCO Object Service Broker for z/OS 5.0.0.
======================================================================
Closed Issues in 5.0.0_hotfix08 (This Release)
CR 1-9ZCDPH
Invalid rows are being built for secondary indexes where binary fields are encountered with the top bit on. This has been fixed.
Customers who have used the batch utility S6BBRSIX/HRNBRSIX at 5.0.0 Hotfix 3 or later to build binary secondary index fields should rebuild their secondary indexes in order to ensure that the secondary indexes are built correctly if the base data was previously loaded by S6BBRTBL/HRNBRTBL.
======================================================================
Closed Issues in 5.0.0_hotfix06
CR 1-8H7LSA
An element for an XML document had both an attribute and data under the element. This has been fixed.
CR 1-8WR8NR
Unable to logon with password encryption exit enabled. This has been fixed.
CR 1-8YX4AT
From the Eclipse UI the table data editor cannot update date field values if the date format is different from "YYYY-MM-DD" in the back end. This has been fixed.
CR 1-917MOB
Password not uppercased causing logon failures. This has been fixed.
CR 1-92XS4Q
Unable to start a session to TIBCO Object Service Broker by means of the IMS TM interface. This has been fixed.
CR 1-937IAK
Problems canceling ODBC connections. This has been fixed.
CR 1-94NTQZ
Messages were lost as a result of timing issues in HDRSBCLI. This has been fixed.
CR 1-94W87
Refines the COMMAREA validity checking so HLLI clients can use one MAP table for both the header and the data.
CR 1-94V383
DOB abends with a S0C4 when viewing resources via ADMIN utility. This has been fixed.
CR 1-96J79Y
Communications services were not initializing under z/OS 1.10. This has been fixed.
CR 1-98NZEH
ODBC Adapter was unable to handle external table types and stored selection. This has been fixed.
CR 1-98TJO8
Bitmap status of pages at commit and checkpoint was not being validated. This has been fixed.
CR 1-9EUZSF
Fixes a problem with incorrect number of arguments being called from ODBC stored procedure test driver.
CR 1-9F7PO2
Corrects logon/logoff timing problems in the EE when under heavy load.
CR 1-9H3MKA
U4080-252 abend was occurring when trying to reset a socket bit that was already reset.This has been fixed.
CR 1-9H3ML4
Random abends were occurring in HCSCNARH. This has been fixed.
CR 1-9H3MLP
Cell storage chains were not being checked. This has been fixed.
CR 1-9HD8XO
Canceluser problems were occurring under heavy load. This has been fixed.
CR 1-9KF56K
OIG messages from .NET containing dates with timestamps failed conversion in ECTSLOADDATA. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix05
CR 1-9FS2JY
A problem was occurring at transaction end when an invalid handle was passed to EMS. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix04
CR 1-8SJWO5
There was no support for ALLOWUSERKEYCSA=N. This has been fixed.
NOTE: Although this z/OS option can be changed dynamically by the use of an z/OS operator commands without an IPL, TIBCO Object Service Broker for z/OS requires an IPL of the system to run properly. This is because a structure would be built in CSA with the appropriate key depending on the setting of the option; changing the option after OSB was started could cause problems. Consequently an IPL is required to get rid of the structure in CSA.
CR 1-8YXEI9
A S0C2 abend was occurring in S6BIMSC2. This has been fixed.
CR 1-8ZHPWQ
A SOC4 abend was occurring in S6BCMCSM. This has been fixed.
CR 1-92933F
When EE sessions were canceled, perhaps due to losterm conditions, the Language Environment thread/enclaves were not cleaned up correctly. This has been fixed.
CR 1-90DXIS
The Data Object Broker was running out of stealable pages. This has been fixed.
CR 1-91QXNX
Insufficient memory was available to run Data Object Broker to Data Object Broker transactions in certain conditions. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix3
CR 1-82EML3
All external servers with type HRN were being left in an "IN-USE" state even when no connections were active. This has been fixed.
CR 1-8CL74P
COUNTOCCURRENCES on a Subview was ignoring the LOCK MODE setting. This has been fixed.
CR 1-8I6JYR
The SMF reporting utility S6BSMEJB was truncating SMF type record counts if the number of records exceeded six digits. This has been fixed.
CR 1-8K6T5H
Corrects a problem with a SOC4 occurring when running the TCP Relay utility, S6BRLYGN. This has been fixed.
CR 1-8LCVLF
After a rule to invoke XML parsing has been called to process packed decimal data, the failure "EX057 Error in arithmetic expression; "OVERFLOW" system condition detected" occurs. This has been fixed.
CR 1-8NBQX7
Under a heavy load, the resident page reclaim task was reclaiming and reusing a page that was in use. This has been fixed.
CR 1-8NKKEQ
A socket connection request is being incorrectly rejected. This has been fixed.
CR 1-8O7G4D
S6BBRSIX could not build an index for a PL9 field nor could S6BBRTBL load such a field into a TDS table. This has been fixed.
CR 1-8OUXR9
Checkpoint was failing because a write was attempting to go beyond the end of file on the cache data set. This has been fixed.
CR 1-8QTQCB
Interval counts for SMF subtype 28 record were seldom being updated. This has been fixed.
CR 1-8TQF4B
Standby sessions were not properly cleaned up and SOC4 were occurring when many users were accessing the system. This has been fixed.
CR 1-8U83HF
Insufficient saveareas in the DOB ESTAE was causing a SOC6 in the main DOB ESTAE routine. This has been fixed.
CR 1-8V8YYL
ODBC Adapter does not work in browse mode. This has been fixed.
CR 1-8VE8ZC
The S6BBRPTR utility was ending with RC=0 even when errors were encountered. This has been fixed.
CR 1-8XP7D4
SMF header field for Subsystem Identification (SSI) was inconsistent between Execution Environment and Data Object Broker records. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix2
CR 1-8N8ZLA
Corrects a S0C4 in HRNCR210 during a DOB peer connection so that the field COMMTRMN is populated with the correct data or left with blanks if no logon data is supplied.
======================================================================
Closed Issues in 5.0.0_hotfix1
CR 1-8JH7BE
License keys are no longer required and have been deactivated.
The purpose of Object Service Broker for z/OS Hotfix01 is to remove the key dependency for customers which have requirements to execute the software on different machines at different locations. Examples of this type of requirement include the following:
* disaster recovery operations that involve a hot or warm backup site
* merged operations resulting from acquisition activities
* sites which stage their applications across several different environments such as Test, Quality Assurance, Promotion, and Production.
Hotfix01 removes all License Key dependencies regarding CPU Serial Number and Site specific checks.
This Hotfix should be provided to customers who experience key-related issues such as described above.
======================================================================
Resolution
==========
Download Hotfix 8 for TIBCO Object Service Broker for z/OS 5.0.0 and apply to your system. Follow the instructions in the README supplied as part of the HotFix package.
Note that hotfixes are cumulative and contain maintenance issued up to this particular hotfix. Consult the README for additional information regarding previous maintenance included in Hotfix 8. TIBCO recommends applying all previous Hotfix maintenance prior to applying the Hotfix 8 maintenance.
If necessary, please open a service request with TIBCO Support for assistance installing this Hotfix.
Obtaining the Hotfix
====================
To download Hotfix 8, go to ftp://support-ftp.tibco.com using the browser or FTP client of your choice. You will be prompted for your userid and password, the same as required to open a Service Request.
Select available_downloads
Select Mainframe
Select OSB
Select 5.0.0
You should then be able to see and download the fix:
TIB_osb_5.0.0_zos_hotfix8.zip
Unzip and upload the hotfix using BINARY file transfer to z/OS as documented in the OSTARXMT documentation.
Reference:
=========
Dataset: TIB_osb_5.0.0_zos_hotfix8.zip
Issues Corrected by Hotfix 8:
=============================
=====================================================================
Product Name: TIBCO(R) Object Service Broker for z/OS
Release Version: 5.0.0_hotfix08
Release Date: July 2009
======================================================================
Introduction
Hotfixes are cumulative. This hotfix includes all previous hotfixes for TIBCO Object Service Broker for z/OS 5.0.0.
======================================================================
Closed Issues in 5.0.0_hotfix08 (This Release)
CR 1-9ZCDPH
Invalid rows are being built for secondary indexes where binary fields are encountered with the top bit on. This has been fixed.
Customers who have used the batch utility S6BBRSIX/HRNBRSIX at 5.0.0 Hotfix 3 or later to build binary secondary index fields should rebuild their secondary indexes in order to ensure that the secondary indexes are built correctly if the base data was previously loaded by S6BBRTBL/HRNBRTBL.
======================================================================
Closed Issues in 5.0.0_hotfix06
CR 1-8H7LSA
An element for an XML document had both an attribute and data under the element. This has been fixed.
CR 1-8WR8NR
Unable to logon with password encryption exit enabled. This has been fixed.
CR 1-8YX4AT
From the Eclipse UI the table data editor cannot update date field values if the date format is different from "YYYY-MM-DD" in the back end. This has been fixed.
CR 1-917MOB
Password not uppercased causing logon failures. This has been fixed.
CR 1-92XS4Q
Unable to start a session to TIBCO Object Service Broker by means of the IMS TM interface. This has been fixed.
CR 1-937IAK
Problems canceling ODBC connections. This has been fixed.
CR 1-94NTQZ
Messages were lost as a result of timing issues in HDRSBCLI. This has been fixed.
CR 1-94W87
Refines the COMMAREA validity checking so HLLI clients can use one MAP table for both the header and the data.
CR 1-94V383
DOB abends with a S0C4 when viewing resources via ADMIN utility. This has been fixed.
CR 1-96J79Y
Communications services were not initializing under z/OS 1.10. This has been fixed.
CR 1-98NZEH
ODBC Adapter was unable to handle external table types and stored selection. This has been fixed.
CR 1-98TJO8
Bitmap status of pages at commit and checkpoint was not being validated. This has been fixed.
CR 1-9EUZSF
Fixes a problem with incorrect number of arguments being called from ODBC stored procedure test driver.
CR 1-9F7PO2
Corrects logon/logoff timing problems in the EE when under heavy load.
CR 1-9H3MKA
U4080-252 abend was occurring when trying to reset a socket bit that was already reset.This has been fixed.
CR 1-9H3ML4
Random abends were occurring in HCSCNARH. This has been fixed.
CR 1-9H3MLP
Cell storage chains were not being checked. This has been fixed.
CR 1-9HD8XO
Canceluser problems were occurring under heavy load. This has been fixed.
CR 1-9KF56K
OIG messages from .NET containing dates with timestamps failed conversion in ECTSLOADDATA. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix05
CR 1-9FS2JY
A problem was occurring at transaction end when an invalid handle was passed to EMS. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix04
CR 1-8SJWO5
There was no support for ALLOWUSERKEYCSA=N. This has been fixed.
NOTE: Although this z/OS option can be changed dynamically by the use of an z/OS operator commands without an IPL, TIBCO Object Service Broker for z/OS requires an IPL of the system to run properly. This is because a structure would be built in CSA with the appropriate key depending on the setting of the option; changing the option after OSB was started could cause problems. Consequently an IPL is required to get rid of the structure in CSA.
CR 1-8YXEI9
A S0C2 abend was occurring in S6BIMSC2. This has been fixed.
CR 1-8ZHPWQ
A SOC4 abend was occurring in S6BCMCSM. This has been fixed.
CR 1-92933F
When EE sessions were canceled, perhaps due to losterm conditions, the Language Environment thread/enclaves were not cleaned up correctly. This has been fixed.
CR 1-90DXIS
The Data Object Broker was running out of stealable pages. This has been fixed.
CR 1-91QXNX
Insufficient memory was available to run Data Object Broker to Data Object Broker transactions in certain conditions. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix3
CR 1-82EML3
All external servers with type HRN were being left in an "IN-USE" state even when no connections were active. This has been fixed.
CR 1-8CL74P
COUNTOCCURRENCES on a Subview was ignoring the LOCK MODE setting. This has been fixed.
CR 1-8I6JYR
The SMF reporting utility S6BSMEJB was truncating SMF type record counts if the number of records exceeded six digits. This has been fixed.
CR 1-8K6T5H
Corrects a problem with a SOC4 occurring when running the TCP Relay utility, S6BRLYGN. This has been fixed.
CR 1-8LCVLF
After a rule to invoke XML parsing has been called to process packed decimal data, the failure "EX057 Error in arithmetic expression; "OVERFLOW" system condition detected" occurs. This has been fixed.
CR 1-8NBQX7
Under a heavy load, the resident page reclaim task was reclaiming and reusing a page that was in use. This has been fixed.
CR 1-8NKKEQ
A socket connection request is being incorrectly rejected. This has been fixed.
CR 1-8O7G4D
S6BBRSIX could not build an index for a PL9 field nor could S6BBRTBL load such a field into a TDS table. This has been fixed.
CR 1-8OUXR9
Checkpoint was failing because a write was attempting to go beyond the end of file on the cache data set. This has been fixed.
CR 1-8QTQCB
Interval counts for SMF subtype 28 record were seldom being updated. This has been fixed.
CR 1-8TQF4B
Standby sessions were not properly cleaned up and SOC4 were occurring when many users were accessing the system. This has been fixed.
CR 1-8U83HF
Insufficient saveareas in the DOB ESTAE was causing a SOC6 in the main DOB ESTAE routine. This has been fixed.
CR 1-8V8YYL
ODBC Adapter does not work in browse mode. This has been fixed.
CR 1-8VE8ZC
The S6BBRPTR utility was ending with RC=0 even when errors were encountered. This has been fixed.
CR 1-8XP7D4
SMF header field for Subsystem Identification (SSI) was inconsistent between Execution Environment and Data Object Broker records. This has been fixed.
======================================================================
Closed Issues in 5.0.0_hotfix2
CR 1-8N8ZLA
Corrects a S0C4 in HRNCR210 during a DOB peer connection so that the field COMMTRMN is populated with the correct data or left with blanks if no logon data is supplied.
======================================================================
Closed Issues in 5.0.0_hotfix1
CR 1-8JH7BE
License keys are no longer required and have been deactivated.
The purpose of Object Service Broker for z/OS Hotfix01 is to remove the key dependency for customers which have requirements to execute the software on different machines at different locations. Examples of this type of requirement include the following:
* disaster recovery operations that involve a hot or warm backup site
* merged operations resulting from acquisition activities
* sites which stage their applications across several different environments such as Test, Quality Assurance, Promotion, and Production.
Hotfix01 removes all License Key dependencies regarding CPU Serial Number and Site specific checks.
This Hotfix should be provided to customers who experience key-related issues such as described above.
======================================================================
Resolution
==========
Download Hotfix 8 for TIBCO Object Service Broker for z/OS 5.0.0 and apply to your system. Follow the instructions in the README supplied as part of the HotFix package.
Note that hotfixes are cumulative and contain maintenance issued up to this particular hotfix. Consult the README for additional information regarding previous maintenance included in Hotfix 8. TIBCO recommends applying all previous Hotfix maintenance prior to applying the Hotfix 8 maintenance.
If necessary, please open a service request with TIBCO Support for assistance installing this Hotfix.
Obtaining the Hotfix
====================
To download Hotfix 8, go to ftp://support-ftp.tibco.com using the browser or FTP client of your choice. You will be prompted for your userid and password, the same as required to open a Service Request.
Select available_downloads
Select Mainframe
Select OSB
Select 5.0.0
You should then be able to see and download the fix:
TIB_osb_5.0.0_zos_hotfix8.zip
Unzip and upload the hotfix using BINARY file transfer to z/OS as documented in the OSTARXMT documentation.
Reference:
=========
Dataset: TIB_osb_5.0.0_zos_hotfix8.zip
Issue/Introduction
Hotfix 8 for TIBCO Object Service Broker for z/OS 5.0.0 is now available.
Environment
Product: TIBCO Object Service Broker for z/OS
Version: 5.0.0
OS: z/OS
--------------------
Feedback
Yes
No
Powered by
