APAR status
Closed as suggestion for future release.
Error description
Though no execution is done on conductor node, its JDBC connection was kept alive during player nodes running. This enhancement provides an option to close the connection in the conductor process before player processes start processeing records, and connect again if necessary after the player processes have completed processing the records.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
Introduced a new property named "Keep conductor connection alive". When the value of this property is "No", close conductor node's connection during player nodes running.
APAR Information
APAR number
JR51754
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
B31
Status
CLOSED SUG
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-11-12
Closed date
2014-12-12
Last modified date
2014-12-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.3","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 December 2014