Fixes are available
APAR status
Closed as program error.
Error description
On a heavily loaded system the parallel job monitor process DSD.OshMonitor may not receive a response from JobMonApp within the fixed 10 second timeout after the lead osh process has completed. This results in incorrect row counts being reported for the job. DSD.OshMonitor timeout needs to be configurable.
Local fix
Problem summary
On a heavily loaded system the parallel job monitor process DSD.OshMonitor may not receive a response from JobMonApp within the fixed 10 second timeout after the lead osh process has completed. This results in incorrect row counts being reported for the job.
Problem conclusion
The DSD.OshMonitor timeout needs to be configurable via OSHMON_READ_RETRY environment variable The effective timeout is the product of actual read timeout which is 1 second and the retry count. The default and minimum retry count is 10, setting OSHMON_READ_RETRY to a higher value will increase the effective timeout.
Temporary fix
Comments
APAR Information
APAR number
JR44899
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-27
Closed date
2012-12-14
Last modified date
2013-03-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R850 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021