A fix is available
APAR status
Closed as new function.
Error description
Need to improve performance by reducing processing requirements of DSWaitForJob()
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This impacts users of the DSWaitForJob API routine and by implication customers using sequence jobs which use the routine for synchronisation. **************************************************************** PROBLEM DESCRIPTION: The code which was checking the status of each job in the WaitForJob loop was itself using the API routines which are general purpose and thus not always optimal for getting just the status information **************************************************************** RECOMMENDATION: If performance of a sequence job is causing concern apply the patch for JR52693 ****************************************************************
Problem conclusion
The routine DSWaitForJob was recoded and the status and pid information directly retrieved from the runtime environment rather than using the API routines to get the information.
Temporary fix
Comments
APAR Information
APAR number
JR52693
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-03-03
Closed date
2015-03-23
Last modified date
2015-03-23
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
R910 PSY
UP
R912 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":"9.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
14 October 2021