A fix is available
APAR status
Closed as program error.
Error description
Job sequence can fail intermittently when running a job used "reset if required, then run" option. Sometimes, if the child job needs to be reset, the sequence appears not to wait for the reset to finish, but continues to try and run the job in parallel to the reset action, leading to confusion as to the actual job status.
Local fix
This fix is included in 8.0.1 fixpack 3
Problem summary
**************************************************************** USERS AFFECTED: All platforms. When a sequence job spawns many instances of a job and one or more of the instances are reset, the sequence may get a status of 99 for the reset instances **************************************************************** PROBLEM DESCRIPTION: The status reported by the sequence job for a child job instances is 99. When sequence jobs start many instances of a job simultaneously causing the system to be under heavy load, there is a timing window when the parent job will fail to read the actual status of the job if it was resetting. The job instances is resetting, but before it could write its status to file, the parent job is already reading the status. Since the child job has not written it, the empty status of 99 is returned. **************************************************************** RECOMMENDATION: patch JR30015v5 is required. This fix was rolled up with JR30015. There will be no separate patch for 34110. This change is included in 8.1 Fix Pack 1. ****************************************************************
Problem conclusion
The parent job should wait for the child job to signal that it has started before polling for its status. This will ensure that the job is in a 'running' state by the time the parent job is cheking status and will wait till it has finished before retrieving the status. The fix has been applied to 8.1, 8.0.1 (GA, FP1, FP2) - a patch is required.
Temporary fix
Comments
APAR Information
APAR number
JR34110
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-27
Closed date
2009-09-16
Last modified date
2010-12-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SERVER
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R810 PSY
UP
R801 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1"}]
Document Information
Modified date:
07 October 2021