Products | Versions |
---|---|
TIBCO Substation ES | - |
Not Applicable | - |
Description:
This hot fix is cumulative with the hotfixes previously generated for TIBCO Substation ES 2.8.1.
Please note that this hotfix has been updated. If you downloaded the hotfix before 2016/05/24, please do so again.
This hotfix can be downloaded from the TIBCO Product Support file transfer server, mft.tibco.com, using
your username and password for the TIBCO Support Web.
You can use FTP, SFTP (FTP or SFTP use requires an FTP / SFTP client or command-line FTP), or your
web browser at https://mft.tibco.com (requires Java applet support in your browser).
Once logged on you can find the hotfix as follows:
Select AvailableDownloads
Select Adapters
Select Substation
Select 2.8.1
Select hotfix-4
You should then be able to see and download the files:
TIB_substation_2.8.1_zos.sxs.hotfix_#4.zip
TIB_substation_2.8.1_readme_hotfix04.txt
Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.
================================================================================
Closed Issues in 2.8.1 hotfix #4 (This Release)
SSES-1139
After sending a number of large records around the 40K size, and then using
the CICS Request/Reply process the request will report an invalid length error.
This have been corrected where the EXCI call now sets the lengths correctly.
The maximum length for DPL requests using a DFHCOMMAREA is 32507.
SSES-1137 - High
Fixed CICS HVT SXCQWRIT trace messages that gets printed to CICS CEEOUT for
each Trigger process.
SSES-1131 - High
CICS Invocation - MRO (type 9)
When using MOI 9, CICS interface assigns the wrong length internally.
Only happens when multiple size inputs have a range less and greater than 32K
The result in a SXC3102W message in the Substation log which is incorrect.
Resolved.
SSES-942 - High
SXG1420E Thread Creation Error Name.
This message appears in the Substation log when z/OS gets confused due to
many threads starting concurrently.
This has now been resolved by retrying the thread create function internally.