JR32648: DSGETJOBINFO WITH DSJ.JOBELAPSED OPTION NOT PICKING UP CORRECT TIME WHEN JOB RAN THRU MIDNIGHT

APAR status

• Closed as program error.

Error description

• DS 753 SUN Solaris (reproduced inhouse on Windows)
  
  If you run a DSGetJobInfo with DSJ.JOBELAPSED against a job
  which was running at midnight, the command retrieves "0" instead
  of the correct amount of time.
  

Local fix

• This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Code that calls server API function DSGetJobInfo() using the
  keyDSJ.JOBELAPSED, to measure the time of long-running jobs
  whose  start and end events occur on different dates.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Code that calls DSGetJobInfo(handle, DSJ.JOBELAPSED) against
  long-running jobs will return a time of 0 if the job finishes
  onen it started. It is supposed to return   HH:MM:SS always,
  even if HH is > 24.
  ****************************************************************
  RECOMMENDATION:
  Apply patch JR32648
  This fix is included in 8.1 FP1
  ****************************************************************
  

Problem conclusion

• Code in DSGetJobInfo.B module was not adding the number of
  seconds per day to the elapsed time if the start and end times
  occured on different days.
  

Temporary fix

Comments

APAR Information

• 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

• R751 PSY

     UP

• R753 PSY

     UP

• R801 PSY

     UP

• R810 PSY

     UP