JR43364: DATASTAGE NOT REPORTING CORRECT ROW COUNTS SPECIFICALLY IF TARGET HAS A REJECT LINK WITH A PEEK STAGE ATTACHED TO IT.

APAR status

• Closed as program error.

Error description

• Row Counts
  If a Peek stage is attached downstream of a database stage which
  is acting as an output for a parallel job, then currently the
  database stage is ignored in terms of recording link info. Only
  the Peek will be monitored, since it looks to ODB like the
  actual target. The database stage will not be counted as a
  target stage as far as the Operational Database is concerned.
  
  The main consequence of this is that the TotalRowsProduced field
  of a job run will contain a number that is less than it should
  be. Instead of counting the sum of the rows being sent to the
  database stage and the peek stage, ODB will count only the
  rejected rows sent to the peek stage. So for example if no rows
  are rejected, the job run may appear to have produced no rows at
  all since the count of rows to the peek stage will be zero.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Customers using the Operations Console to view DataStage jobs
  containing a target stage, such as database or  connector, where
  that stage uses a reject link.
  ****************************************************************
  PROBLEM DESCRIPTION:
  If a stage such as Peek is attached downstream of a database
  stage which is acting as an output for a parallel job, then the
  database stage can be ignored in terms of recording row counts.
  (This topology will mainly occur if the downstream stage is a
  reject link for the database stage.) Only the Peek will be
  treated as a target stage, and the count of total rows produced
  by the job will not include those sent to the database stage,
  only to its reject link. This will often mean that the number of
  rows produced is recorded as zero, and shown as such in the
  Operations Console.
  ****************************************************************
  RECOMMENDATION:
  Apply the  patch or fix pack. It is not necessary to recompile
  affected jobs, and subsequent runs should correctly record the
  total rows produced.
  ****************************************************************
  

Problem conclusion

• Change the analysis of the job design so that stage types marked
  as "passive" internally are always treated as potential
  sources/targets even if they appear to have both input and
  output links. This marker is picked up the next time the job is
  compiled; if missing, it is calculated dynamically each time the
  job is run.
  

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:

Fix information

• Fixed component name

  INFO SRVR PLATF

• Fixed component ID

  5724Q3612

Applicable component levels

• R870 PSY

     UP

• R910 PSY

     UP